CVE-2026-47270

MEDIUMNVD 6.36.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 6.3 under NVD CVSS v3. EPSS exploit probability: 0.1% (1st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2026-32655 (ENISA EUVD)Source: ENISA EUVD

6.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 6.3Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

pam_usb provides hardware authentication for Linux using ordinary removable media. Prior to 0.9.0, pam_usb is a PAM module loaded into the host process (sudo, login, GDM, GNOME Shell). Display managers such as GDM run multiple concurrent authentication threads. Three functions used by the deny_remote feature called the non-reentrant strtok(), which stores state in a single global pointer. If two authentications race, one thread's strtok() call can overwrite the other's in-progress tokenisation pointer, causing incorrect parsing of the tmux session data or the /proc environ scan that backs the remote-session detection logic. Additionally, pusb_tmux_get_client_tty() passed the raw pointer returned by getenv(TMUX) directly to strtok(). getenv() returns a pointer into the live process environment block; strtok() inserts NUL bytes into that block, permanently corrupting the TMUX variable for subsequent code running in the same process. In long-lived display managers this affects all future authentications in that process. The combined effect can cause deny_remote=true to return an incorrect decision for a remote session, or an incorrect decision for a local session, depending on thread interleaving. This vulnerability is fixed in 0.9.0.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
28
EG Risk 28/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity63% × 45%
Impact severity (EG Severity): CVSS 6.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.3): severity, escalated by confirmed exploitation. This CVE's 6.3 is its impact severity (EG Severity), not escalated.

EG Severity
6.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 27, 2026

Last Modified

October 26, 2026

Advisory Details (3)

Auto-updated Jun 13, 2026
Fix named in the CVE record. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

strtok() race condition in multi-threaded PAM hosts can corrupt deny_remote result · Advisory · mcdope/pam_usb · GitHub

https://github.com/mcdope/pam_usb/security/advisories/GHSA-j3xw-vc43-x7jg
GitHub commit

commit d003e551b794 (mcdope/pam_usb)

Fix landed in mcdope/pam_usb commit d003e551b794 — awaiting tagged release

https://github.com/mcdope/pam_usb/commit/d003e551b794a9e3774ff4720830fb7aadaa48bd
GitHub commit

commit 94f1640a61d4 (mcdope/pam_usb)

Fix landed in mcdope/pam_usb commit 94f1640a61d4 — awaiting tagged release

https://github.com/mcdope/pam_usb/commit/94f1640a61d49dfaf38e782680a52f01d5bf8b51

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 28× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 187 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 87 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-47270?
CVE-2026-47270 is a medium-severity vulnerability; its CVE record was published on May 27, 2026. pam_usb provides hardware authentication for Linux using ordinary removable media. Prior to 0.9.0, pam_usb is a PAM module loaded into the host process (sudo, login, GDM, GNOME Shell). Display managers such as GDM run multiple concurrent authentication threads. Three functions used by the…
When was the CVE record for CVE-2026-47270 published?
The CVE record for CVE-2026-47270 was published on May 27, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 26, 2026; the record at its source may have been updated since.
Is CVE-2026-47270 actively exploited?
CVE-2026-47270 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47270?
CVE-2026-47270 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-47270?
The CVE record for CVE-2026-47270 names the fix: "This vulnerability is fixed in 0.9.0."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-47270

Explore →

Is Your Infrastructure Affected by CVE-2026-47270?

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

Book a Demo →Browse All CVEs