CVE-2026-54411

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

Score 5.9 from GitHub Security Advisory published 2026-06-14. a secondary CVSS source baseline 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.9Exploit: None knownExposed: 0

A fix is available — apply it.

Linux-PAM through 1.7.2 contains an observable timing discrepancy (CWE-208) in the pam_userdb module's plaintext-password comparison path in modules/pam_userdb/pam_userdb.c that allows a local or network-adjacent attacker able to repeatedly drive authentication through a calling service to recover the plaintext password of a target account by measuring response-timing differences.

CVSS v3
5.9
EG Score
5.9(medium)
EG Risk
27(Track)
EG Risk 27/100SSVC: Track

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
Severity59% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

June 14, 2026

Last Modified

August 10, 2026

Advisory Details (4)

Auto-updated Jun 15, 2026
No patch confirmed yet.
generic

CWE - CWE-208: Observable Timing Discrepancy (4.20)

https://cwe.mitre.org/data/definitions/208.html
generic

linux-pam/libpam/include/pam_inline.h at master · linux-pam/linux-pam · GitHub

https://github.com/linux-pam/linux-pam/blob/master/libpam/include/pam_inline.h
generic

linux-pam/modules/pam_userdb/pam_userdb.c at master · linux-pam/linux-pam · GitHub

https://github.com/linux-pam/linux-pam/blob/master/modules/pam_userdb/pam_userdb.c#L327
generic

GitHub - linux-pam/linux-pam: Linux PAM (Pluggable Authentication Modules for Linux) project · GitHub

https://github.com/linux-pam/linux-pam

Vendor Advisories for CVE-2026-54411(5)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibpam0g-dev (1.4.0-11ubuntu2.7) @ jammy2026-08-24ubuntu
redhatpam-0:1.3.1-40.el8_102026-08-18redhat
redhatpam-main-1.7.2-2.2.hum12026-07-02redhat
redhatpam-main-1.7.2-1.1.hum12026-04-10redhat

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 rangeFixed inDependents
pam1.4.0-10 ... 1.7.0-8 (34 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
pam1.5.2-6 ... 1.7.0-8 (24 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
pam1.7.0-5, 1.7.0-6, 1.7.0-7, 1.7.0-8——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
pam1.7.0-5, 1.7.0-6, 1.7.0-7, 1.7.0-8——

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

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 20× in last 7d / 103× 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 223 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-54411?
CVE-2026-54411 is a medium vulnerability published on June 14, 2026. Linux-PAM through 1.7.2 contains an observable timing discrepancy (CWE-208) in the pamuserdb module's plaintext-password comparison path in modules/pamuserdb/pam_userdb.c that allows a local or network-adjacent attacker able to repeatedly drive authentication through a calling service to recover…
When was CVE-2026-54411 disclosed?
CVE-2026-54411 was first published in the National Vulnerability Database on June 14, 2026, with the most recent update on August 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54411 actively exploited?
CVE-2026-54411 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 74.3% of all scored CVEs.
What is the CVSS score of CVE-2026-54411?
CVE-2026-54411 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-54411?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54411, 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-2026-54411

Explore →

Is Your Infrastructure Affected by CVE-2026-54411?

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

Start Free Scan →Browse All CVEs