CVE-2025-9486

LOWPre-NVD 3.33.3—
EchelonGraph scoreMEDIUM confidence

Score 3.3 from GitHub Security Advisory (severity: LOW) published 2026-08-12. A secondary CVSS source baseline 3.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
3.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 3.3Exploit: Elevated riskExposed services: Not assessed

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

GitLab has remediated an issue in GitLab EE affecting all versions from 15.6 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under certain conditions could have allowed a user with a pending membership to receive permissions granted by a custom role, due to incorrect privilege assignment that did not account for membership state.

CVSS v3
3.3
EG Score
3.3LOWmedium confidence
EG Risk
31
EG Risk 31/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity33% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
25th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 12, 2026

Last Modified

September 29, 2026

Vendor Advisories for CVE-2025-9486(2)

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 / 39× 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-10-04 23:21 UTCEPSS rescore
  2. 2026-10-03 14:25 UTCEPSS rescore
  3. 2026-10-02 08:20 UTCEG score recompute
  4. 2026-10-02 08:19 UTCGHSA enrichment
  5. 2026-10-01 19:49 UTCEPSS rescore
  6. 2026-09-30 15:02 UTCEPSS rescore
  7. 2026-09-29 15:20 UTCEPSS rescore
  8. 2026-09-29 10:14 UTCEG score recompute
  9. 2026-09-29 10:14 UTCGHSA enrichment
  10. 2026-09-28 13:50 UTCEPSS rescore
  11. 2026-09-27 09:53 UTCEG score recompute
  12. 2026-09-27 09:53 UTCGHSA enrichment
  13. 2026-09-26 15:58 UTCEPSS rescore
  14. 2026-09-24 02:50 UTCEG score recompute
  15. 2026-09-24 02:50 UTCGHSA enrichment
  16. 2026-09-23 13:47 UTCEPSS rescore
  17. 2026-09-21 09:53 UTCEG score recompute
  18. 2026-09-21 09:53 UTCGHSA enrichment
  19. 2026-09-20 20:15 UTCEPSS rescore
  20. 2026-09-18 19:27 UTCEPSS rescore
  21. 2026-09-18 16:57 UTCEG score recompute
  22. 2026-09-18 16:57 UTCGHSA enrichment
  23. 2026-09-16 05:14 UTCEPSS rescore
  24. 2026-09-15 22:28 UTCEG score recompute
  25. 2026-09-15 22:28 UTCGHSA enrichment
Show 55 more
  1. 2026-09-13 16:46 UTCEPSS rescore
  2. 2026-09-13 05:30 UTCEG score recompute
  3. 2026-09-13 05:30 UTCGHSA enrichment
  4. 2026-09-12 15:00 UTCEPSS rescore
  5. 2026-09-11 14:52 UTCEPSS rescore
  6. 2026-09-11 09:36 UTCEPSS rescore
  7. 2026-09-10 12:33 UTCEG score recompute
  8. 2026-09-10 12:33 UTCGHSA enrichment
  9. 2026-09-10 09:34 UTCEPSS rescore
  10. 2026-09-08 22:00 UTCEPSS rescore
  11. 2026-09-07 17:36 UTCEG score recompute
  12. 2026-09-07 17:36 UTCGHSA enrichment
  13. 2026-09-07 16:01 UTCEPSS rescore
  14. 2026-09-06 13:47 UTCEPSS rescore
  15. 2026-09-05 00:40 UTCEG score recompute
  16. 2026-09-05 00:40 UTCGHSA enrichment
  17. 2026-09-04 05:06 UTCEPSS rescore
  18. 2026-09-02 14:11 UTCEPSS rescore
  19. 2026-09-02 06:18 UTCEG score recompute
  20. 2026-09-02 06:18 UTCGHSA enrichment
  21. 2026-09-01 13:53 UTCEPSS rescore
  22. 2026-09-01 04:39 UTCEPSS rescore
  23. 2026-08-30 19:17 UTCEPSS rescore
  24. 2026-08-30 12:42 UTCEG score recompute
  25. 2026-08-30 12:42 UTCGHSA enrichment
  26. 2026-08-30 01:21 UTCEPSS rescore
  27. 2026-08-28 21:40 UTCEPSS rescore
  28. 2026-08-27 19:36 UTCEG score recompute
  29. 2026-08-27 19:36 UTCGHSA enrichment
  30. 2026-08-27 14:24 UTCEPSS rescore
  31. 2026-08-25 13:48 UTCEPSS rescore
  32. 2026-08-25 02:40 UTCEG score recompute
  33. 2026-08-25 02:39 UTCGHSA enrichment
  34. 2026-08-23 00:19 UTCEPSS rescore
  35. 2026-08-22 09:43 UTCEG score recompute
  36. 2026-08-22 09:43 UTCGHSA enrichment
  37. 2026-08-21 23:48 UTCEPSS rescore
  38. 2026-08-20 22:55 UTCEPSS rescore
  39. 2026-08-19 17:03 UTCEPSS rescore
  40. 2026-08-19 16:46 UTCGHSA enrichment
  41. 2026-08-18 15:09 UTCEG score recompute
  42. 2026-08-18 15:08 UTCGHSA enrichment
  43. 2026-08-16 14:56 UTCEPSS rescore
  44. 2026-08-16 06:33 UTCEG score recompute
  45. 2026-08-16 06:33 UTCGHSA enrichment
  46. 2026-08-16 02:14 UTCEPSS rescore
  47. 2026-08-15 01:30 UTCEPSS rescore
  48. 2026-08-13 22:00 UTCEPSS rescore
  49. 2026-08-13 13:36 UTCEG score recompute
  50. 2026-08-13 13:36 UTCGHSA enrichment
  51. 2026-08-13 12:47 UTCEG score recompute
  52. 2026-08-13 12:47 UTCGHSA enrichment
  53. 2026-08-12 20:20 UTCEG score recompute
  54. 2026-08-12 19:21 UTCEG score recompute
  55. 2026-08-12 19:20 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2025-9486?
CVE-2025-9486 is a low vulnerability published on August 12, 2026. GitLab has remediated an issue in GitLab EE affecting all versions from 15.6 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under certain conditions could have allowed a user with a pending membership to receive permissions granted by a custom role, due to incorrect privilege…
When was CVE-2025-9486 disclosed?
CVE-2025-9486 was first published on August 12, 2026, with the most recent update on September 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-9486 actively exploited?
CVE-2025-9486 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (25th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-9486?
CVE-2025-9486 has a CVSS base score of 3.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-9486?
No fix for CVE-2025-9486 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2025-9486 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-9486?

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