CVE-2024-39930

CRITICALNVD 9.99.9—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.9 under NVD CVSS v3. EPSS exploit probability: 11.9%, top 6% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.9
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 7%CVSS: 9.9Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The built-in SSH server of Gogs through 0.13.0 allows argument injection in internal/ssh/ssh.go, leading to remote code execution. Authenticated attackers can exploit this by opening an SSH connection and sending a malicious --split-string env request if the built-in SSH server is activated. Windows installations are unaffected.

CVSS v3
9.9
EG Score
9.9(medium)
EG Risk
—
EPSS
93.7%
KEV
Not listed

Published

July 4, 2024

Last Modified

April 11, 2025

Advisory Details (3)

Auto-updated Jul 20, 2026
⚠️ Active exploitation confirmed. No patch confirmed yet.
generic🟡 PoC Available

Argument injection in Gogs SSH server (CVE-2024-39930) - vsociety

https://www.vicarius.io/vsociety/posts/argument-injection-in-gogs-ssh-server-cve-2024-39930
generic🔴 Active Exploitation

Securing Developer Tools: Unpatched Code Vulnerabilities in Gogs (1/2) | Sonar

https://www.sonarsource.com/blog/securing-developer-tools-unpatched-code-vulnerabilities-in-gogs-1/
generic

Releases · gogs/gogs · GitHub

https://github.com/gogs/gogs/releases

Affected Packages

(2 across 1 ecosystem)
Go(2)
PackageVulnerable rangeFixed inDependents
github.com/gogs/gogs———
gogs.io/gogs—0.13.1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 45× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 14:07 UTCEPSS rescore
  2. 2026-07-22 14:07 UTCEPSS rescore
  3. 2026-07-21 15:23 UTCEPSS rescore
  4. 2026-07-21 15:23 UTCEPSS rescore
  5. 2026-07-20 17:06 UTCEPSS rescore
  6. 2026-07-19 14:30 UTCEPSS rescore
  7. 2026-07-19 14:30 UTCEPSS rescore
  8. 2026-07-19 02:28 UTCEPSS rescore
  9. 2026-07-19 02:28 UTCEPSS rescore
  10. 2026-07-18 10:03 UTCEPSS rescore
  11. 2026-07-16 17:02 UTCEPSS rescore
  12. 2026-07-15 16:56 UTCEPSS rescore
  13. 2026-07-15 16:56 UTCEPSS rescore
  14. 2026-07-15 01:59 UTCEPSS rescore
  15. 2026-07-15 01:59 UTCEPSS rescore
  16. 2026-07-14 02:55 UTCOSV refresh
  17. 2026-07-13 22:29 UTCEPSS rescore
  18. 2026-07-12 05:45 UTCEPSS rescore
  19. 2026-07-11 08:26 UTCEPSS rescore
  20. 2026-07-11 08:26 UTCEPSS rescore
  21. 2026-07-09 19:09 UTCEPSS rescore
  22. 2026-07-08 15:14 UTCEPSS rescore
  23. 2026-07-08 15:13 UTCEPSS rescore
  24. 2026-07-07 13:45 UTCEPSS rescore
  25. 2026-07-06 16:26 UTCEPSS rescore
Show 65 more
  1. 2026-07-06 02:22 UTCEPSS rescore
  2. 2026-07-06 02:22 UTCEPSS rescore
  3. 2026-07-05 02:29 UTCEPSS rescore
  4. 2026-07-04 06:30 UTCEPSS rescore
  5. 2026-07-01 15:05 UTCEPSS rescore
  6. 2026-06-30 23:21 UTCEPSS rescore
  7. 2026-06-30 23:21 UTCEPSS rescore
  8. 2026-06-29 14:05 UTCEPSS rescore
  9. 2026-06-28 14:06 UTCEPSS rescore
  10. 2026-06-28 14:06 UTCEPSS rescore
  11. 2026-06-28 04:55 UTCEPSS rescore
  12. 2026-06-28 04:55 UTCEPSS rescore
  13. 2026-06-27 03:07 UTCEPSS rescore
  14. 2026-06-27 03:07 UTCEPSS rescore
  15. 2026-06-26 00:46 UTCOSV refresh
  16. 2026-06-25 13:49 UTCEPSS rescore
  17. 2026-06-24 14:04 UTCEPSS rescore
  18. 2026-06-24 14:04 UTCEPSS rescore
  19. 2026-06-23 21:32 UTCEPSS rescore
  20. 2026-06-23 21:32 UTCEPSS rescore
  21. 2026-06-22 14:25 UTCEPSS rescore
  22. 2026-06-22 14:25 UTCEPSS rescore
  23. 2026-06-19 19:25 UTCEPSS rescore
  24. 2026-06-19 19:25 UTCEPSS rescore
  25. 2026-06-18 17:52 UTCEPSS rescore
  26. 2026-06-18 17:51 UTCEPSS rescore
  27. 2026-06-17 17:52 UTCEPSS rescore
  28. 2026-06-16 17:52 UTCEPSS rescore
  29. 2026-06-16 17:52 UTCEPSS rescore
  30. 2026-06-15 17:47 UTCEPSS rescore
  31. 2026-06-14 23:16 UTCEPSS rescore
  32. 2026-06-13 22:59 UTCEPSS rescore
  33. 2026-06-13 22:59 UTCEPSS rescore
  34. 2026-06-12 23:11 UTCEPSS rescore
  35. 2026-06-11 13:59 UTCEPSS rescore
  36. 2026-06-10 22:17 UTCEPSS rescore
  37. 2026-06-10 13:21 UTCEPSS rescore
  38. 2026-06-08 14:16 UTCEPSS rescore
  39. 2026-06-08 13:42 UTCOSV refresh
  40. 2026-06-06 13:46 UTCEPSS rescore
  41. 2026-06-06 13:46 UTCEPSS rescore
  42. 2026-06-05 22:46 UTCEPSS rescore
  43. 2026-06-05 22:46 UTCEPSS rescore
  44. 2026-06-04 13:11 UTCEPSS rescore
  45. 2026-06-04 13:11 UTCEPSS rescore
  46. 2026-06-02 20:12 UTCEPSS rescore
  47. 2026-06-01 13:51 UTCEPSS rescore
  48. 2026-06-01 13:51 UTCEPSS rescore
  49. 2026-05-31 22:30 UTCEPSS rescore
  50. 2026-05-31 22:30 UTCEPSS rescore
  51. 2026-05-31 00:15 UTCEPSS rescore
  52. 2026-05-31 00:15 UTCEPSS rescore
  53. 2026-05-29 13:43 UTCEPSS rescore
  54. 2026-05-28 13:44 UTCEPSS rescore
  55. 2026-05-28 13:44 UTCEPSS rescore
  56. 2026-05-28 13:44 UTCEPSS rescore
  57. 2026-05-27 13:40 UTCEPSS rescore
  58. 2026-05-27 13:40 UTCEPSS rescore
  59. 2026-05-27 13:40 UTCEPSS rescore
  60. 2026-05-26 13:43 UTCEPSS rescore
  61. 2026-05-26 13:43 UTCEPSS rescore
  62. 2026-05-26 07:18 UTCEPSS rescore
  63. 2026-05-26 07:18 UTCEPSS rescore
  64. 2026-05-26 07:18 UTCEPSS rescore
  65. 2026-05-23 22:57 UTCEG score recompute

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-52348
    First seen Jul 2, 2025

    gogs 0.13.0 - Remote Code Execution (RCE)

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-39930?
CVE-2024-39930 is a critical vulnerability published on July 4, 2024. The built-in SSH server of Gogs through 0.13.0 allows argument injection in internal/ssh/ssh.go, leading to remote code execution. Authenticated attackers can exploit this by opening an SSH connection and sending a malicious --split-string env request if the built-in SSH server is activated.…
When was CVE-2024-39930 disclosed?
CVE-2024-39930 was first published in the National Vulnerability Database on July 4, 2024, with the most recent update on April 11, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-39930 actively exploited?
CVE-2024-39930 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 93.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-39930?
CVE-2024-39930 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2024-39930?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-39930, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-39930

Explore →

Is Your Infrastructure Affected by CVE-2024-39930?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs