Home
» Security vulnerabilities
» CVE-2022-1993
Path Traversal in GitHub repository gogs/gogs prior to 0.12.9.
NVD Status： Modified ，CVE State: published
Threat Intelligence & Risk Assessment for CVE-2022-1993
Conclusion & alert: CVE-2022-1993 is rated High Exploit Risk (82.8/100) : CVSS High severity, with high exploitation likelihood (EPSS 51.14%, 99th percentile).Core evidence: 1 public exploit reference(s) are indexed (Exploit-DB).Mandatory action: Public exploits are available—assess exposure, apply mitigations, and prioritize patching.
Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.
Public exploit references (Exploit-DB) for CVE-2022-1993
EDB-ID
Source
Kind
Published
Link
—
nvd_ref
exploit_tag
Exploit-DB ↗
Exploit prediction scoring system (EPSS) score for CVE-2022-1993
EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).
#
Date
Old EPSS score
New EPSS score
Delta (New - Old)
1
2026-06-25
50.34%
51.14%
+0.80%
2
2026-06-15
0.55%
50.34%
+49.78%
3
2025-07-22
—
0.55%
—
Full EPSS history
(18 records total)
Common vulnerability scoring system (CVSS) metrics for CVE-2022-1993
CVSS metrics for this CVE.
Base score
Version
Severity
Vector
Exploitability
Impact
Score source
8.1
3.1
HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
2.8
5.2
[email protected]
8.1
3.0
HIGH
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
2.8
5.2
[email protected]
5.5
2.0
MEDIUM
AV:N/AC:L/Au:S/C:P/I:P/A:N
Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:S)
A single authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:N)
No availability impact.
8.0
4.9
[email protected]
Weakness enumeration for CVE-2022-1993
GitHub Security Advisory for CVE-2022-1993
GHSA-6vcc-v9vw-g2x5 · Severity: high · Ecosystem: go
— Path Traversal in Git HTTP endpoints in Gogs
OS Trackers for CVE-2022-1993
Affected software / configurations for CVE-2022-1993
Vendor
Product
Version
Raw CPE
gogs
gogs
< 0.12.9
cpe:2.3:a:gogs:gogs:*:*:*:*:*:*:*:*
References for CVE-2022-1993
cvelogic
Threat Intelligence