CVE-2025-3396

MEDIUMNVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

Score 4.3 from GitHub Security Advisory published 2025-07-10. NVD baseline CVSS 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
4.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.3Exploit: NoneExposed: 0

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

An issue has been discovered in GitLab EE affecting all versions from 13.3 before 17.11.6, 18.0 before 18.0.4, and 18.1 before 18.1.2 that could have allowed authenticated project owners to bypass group-level forking restrictions by manipulating API requests.

CVSS v3
4.3
EG Score
4.3(medium)
EPSS
21.3%
KEV
Not listed

Published

July 10, 2025

Last Modified

July 25, 2025

References (2)

Vendor Advisories for CVE-2025-3396(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 47× 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-06 19:19 UTCOSV refresh
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-04 06:30 UTCEPSS rescore
  7. 2026-07-01 15:06 UTCEPSS rescore
  8. 2026-07-01 15:06 UTCEPSS rescore
  9. 2026-06-30 23:22 UTCEPSS rescore
  10. 2026-06-30 23:22 UTCEPSS rescore
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-29 14:06 UTCEPSS rescore
  13. 2026-06-28 14:07 UTCEPSS rescore
  14. 2026-06-28 14:07 UTCEPSS rescore
  15. 2026-06-28 04:55 UTCEPSS rescore
  16. 2026-06-28 04:55 UTCEPSS rescore
  17. 2026-06-27 03:08 UTCEPSS rescore
  18. 2026-06-27 03:08 UTCEPSS rescore
  19. 2026-06-25 13:49 UTCEPSS rescore
  20. 2026-06-25 13:49 UTCEPSS rescore
  21. 2026-06-24 14:04 UTCEPSS rescore
  22. 2026-06-24 14:04 UTCEPSS rescore
  23. 2026-06-23 21:32 UTCEPSS rescore
  24. 2026-06-23 21:32 UTCEPSS rescore
  25. 2026-06-22 14:25 UTCEPSS rescore
Show 40 more
  1. 2026-06-22 14:25 UTCEPSS rescore
  2. 2026-06-21 14:56 UTCEPSS rescore
  3. 2026-06-21 14:56 UTCEPSS rescore
  4. 2026-06-21 01:59 UTCEPSS rescore
  5. 2026-06-21 01:59 UTCEPSS rescore
  6. 2026-06-19 19:25 UTCEPSS rescore
  7. 2026-06-19 19:25 UTCEPSS rescore
  8. 2026-06-18 17:52 UTCEPSS rescore
  9. 2026-06-18 17:52 UTCEPSS rescore
  10. 2026-06-18 07:43 UTCOSV refresh
  11. 2026-06-17 17:52 UTCEPSS rescore
  12. 2026-06-16 17:52 UTCEPSS rescore
  13. 2026-06-16 17:52 UTCEPSS rescore
  14. 2026-06-14 23:17 UTCEPSS rescore
  15. 2026-06-13 23:00 UTCEPSS rescore
  16. 2026-06-12 23:11 UTCEPSS rescore
  17. 2026-06-11 14:00 UTCEPSS rescore
  18. 2026-06-10 22:18 UTCEPSS rescore
  19. 2026-06-10 13:22 UTCEPSS rescore
  20. 2026-06-08 14:16 UTCEPSS rescore
  21. 2026-06-08 14:16 UTCEPSS rescore
  22. 2026-06-07 15:24 UTCEPSS rescore
  23. 2026-06-06 13:47 UTCEPSS rescore
  24. 2026-06-06 13:47 UTCEPSS rescore
  25. 2026-06-05 22:46 UTCEPSS rescore
  26. 2026-06-05 22:46 UTCEPSS rescore
  27. 2026-06-05 06:10 UTCEPSS rescore
  28. 2026-06-05 06:10 UTCEPSS rescore
  29. 2026-06-04 13:12 UTCEPSS rescore
  30. 2026-06-04 13:12 UTCEPSS rescore
  31. 2026-06-02 20:12 UTCEPSS rescore
  32. 2026-06-01 13:51 UTCEPSS rescore
  33. 2026-06-01 13:51 UTCEPSS rescore
  34. 2026-05-31 22:30 UTCEPSS rescore
  35. 2026-05-31 22:30 UTCEPSS rescore
  36. 2026-05-31 00:16 UTCEPSS rescore
  37. 2026-05-30 02:05 UTCEG score recompute
  38. 2026-05-30 02:05 UTCGHSA enrichment
  39. 2026-05-30 00:12 UTCOSV refresh
  40. 2026-05-29 13:44 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-3396?
CVE-2025-3396 is a medium vulnerability published on July 10, 2025. An issue has been discovered in GitLab EE affecting all versions from 13.3 before 17.11.6, 18.0 before 18.0.4, and 18.1 before 18.1.2 that could have allowed authenticated project owners to bypass group-level forking restrictions by manipulating API requests.
When was CVE-2025-3396 disclosed?
CVE-2025-3396 was first published in the National Vulnerability Database on July 10, 2025, with the most recent update on July 25, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-3396 actively exploited?
CVE-2025-3396 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 21.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-3396?
CVE-2025-3396 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2025-3396?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-3396, 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

Explore the affected products and dependency analysis for CVE-2025-3396

Explore →

Is Your Infrastructure Affected by CVE-2025-3396?

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

Start Free Scan →Browse All CVEs