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. The comparison uses strncmp() (or strncasecmp() when PAM_ICASE_ARG is set) preceded by a length-equality check, so the time to reject a candidate depends on the index of the first differing byte and on whether the candidate's length matches the stored password, leaking the password length and individual prefix bytes. The vulnerable path is reached when the administrator configures pam_userdb with crypt=none, with an unrecognized crypt method, or without a crypt= argument, causing the module to store and compare credentials in plaintext.

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

July 24, 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(4)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibpam0g-dev (1.7.0-5ubuntu3.1) @ resolute2026-07-27ubuntu
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.

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 13× in last 7d / 86× 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 123 total refreshes for this CVE.

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

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/pamuserdb.c that allows a local or network-adjacent attacker able to repeatedly drive authentication through a calling service to recover the…
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 July 24, 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

Explore the affected products and dependency analysis for 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