CVE-2026-12505

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-18. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:redhat, epss, ghsa
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was found in the cifs-utils package where the cifs.upcall helper fails to securely drop its root privileges before looking up user information inside a user-controlled environment. A local, low privileged attacker can exploit this by using a crafted request_key payload to trick the root-owned helper into entering a custom environment (namespace) containing a malicious NSS module. This forces the system to load the attacker's controlled NSS Module and configuration, allowing them to execute arbitrary commands as the root user, elevating their privileges and fully compromising the system.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

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
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

Published

June 18, 2026

Last Modified

September 1, 2026

Advisory Details (3)

Auto-updated Jun 18, 2026
Patch available. Sources: redhat.
redhat

2489805 – (CVE-2026-12505) CVE-2026-12505 cifs-utils: local privilege escalation via forged cifs.spnego key description in cifs.upcall

https://bugzilla.redhat.com/show_bug.cgi?id=2489805
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-12505

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntucifs-utils (2:7.0-2ubuntu0.5) @ noble2026-09-14ubuntu
ubuntucifs-utils (2:6.14-1ubuntu0.4) @ jammy2026-09-14ubuntu
redhatrhcos-4.22.9.8.202607220526-02026-07-28redhat
redhatcifs-utils-0:7.0-5.el8_102026-07-15redhat
redhatcifs-utils-0:7.6-2.el9_82026-07-15redhat
redhatcifs-utils-0:7.6-1.el10_22026-06-29redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
cifs-utils2:6.11-3.1 ... 2:7.4-1 (13 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
cifs-utils2:7.0-2 ... 2:7.8-1 (8 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
cifs-utils2:7.4-1, 2:7.8-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
cifs-utils2:7.4-1
  • every version up to 2:7.8-1: fixed in 2:7.8-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 6× in last 7d / 26× 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.

Showing the most recent 100 of 360 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-12505?
CVE-2026-12505 is a high vulnerability published on June 18, 2026. A flaw was found in the cifs-utils package where the cifs.upcall helper fails to securely drop its root privileges before looking up user information inside a user-controlled environment. A local, low privileged attacker can exploit this by using a crafted request_key payload to trick the…
When was CVE-2026-12505 disclosed?
CVE-2026-12505 was first published on June 18, 2026, with the most recent update on September 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-12505 actively exploited?
CVE-2026-12505 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-12505?
CVE-2026-12505 has a CVSS base score of 7.8 (the CNA's own assessment, by redhat; NVD's own analysis pending).
How do I remediate CVE-2026-12505?
A fix for CVE-2026-12505 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-12505 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-12505

Explore →

Is Your Infrastructure Affected by CVE-2026-12505?

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