WaratekVRT Sign in
Reset
More filters (2)
Columns
Including CVEs outside Waratek scope✕EPSS ≥ 0.5✕Product gogs✕
Overview 7 matches · 0 in Waratek scope · 0 protected · 1 exploited · 1 CISA KEV · 3 public PoC
7matches 0in Waratek scope0.0% 0protected0.0% 1exploited14.3% 1CISA KEV14.3% 3public PoC42.9%
Protected by Waratek 0 0.0% Rule in development 0 0.0% Mitigation candidate 0 0.0% No exploit published 0 0.0% Outside Waratek scope 0 0.0% Not applicable 7 100.0% Withdrawn CVE 0 0.0%
Critical 3 42.9% High 4 57.1% Medium 0 0.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 0 0.0% partly blocked 0 0.0% not blocked 7 100.0% not established 0 0.0% unrecorded 0 0.0%
7 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed.
CVE Severity Published▾ Status Exploitation Description
CVE-2025-8110 High 2025-12-10 Not applicable Exploited Improper Symbolic link handling in the PutContents API in Gogs allows Local Execution of Code.
CVE-2024-55947 High 2024-12-23 Not applicable Proof of concept only Gogs is an open source self-hosted Git service. A malicious user is able to write a file to an arbitrary path on the server to gain SSH access to the server. The vulnerability is fixed in 0.13.1.
CVE-2024-39931 Critical 2024-07-04 Not applicable Forecast only Gogs through 0.13.0 allows deletion of internal files.
CVE-2022-2024 Critical 2023-02-25 Not applicable Proof of concept only OS Command Injection in GitHub repository gogs/gogs prior to 0.12.11.
CVE-2022-32174 Critical 2022-10-11 Not applicable Proof of concept only In Gogs, versions v0.6.5 through v0.12.10 are vulnerable to Stored Cross-Site Scripting (XSS) that leads to an account takeover.
CVE-2022-0415 High 2022-03-21 Not applicable Working exploit published Remote Command Execution in uploading repository file in GitHub repository gogs/gogs prior to 0.12.6.
CVE-2020-15867 High 2020-10-16 Not applicable Working exploit published The git hook feature in Gogs 0.5.5 through 0.12.2 allows for authenticated remote code execution. There can be a privilege escalation if access to this hook feature is granted to a user who does not have administrative privileges. NOTE: because this is mentioned in the documentation but not in the UI, it could be considered a "Product UI does not Warn User of Unsafe Actions" issue.