CVE-2026-44713

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 95% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:github_m, epss
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

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

pam_usb provides hardware authentication for Linux using ordinary removable media. Prior to 0.8.7, src/tmux.c reads the user's $TMUX environment variable, splits it on commas, and interpolates the socket-path component directly into a shell command passed to popen(). Because the value is placed inside double-quotes without sanitisation, any value containing " terminates the quoted string and injects arbitrary shell syntax. popen() runs as root inside the PAM stack. This vulnerability is fixed in 0.8.7.

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
5.3%
KEV
Not listed

Published

May 27, 2026

Last Modified

May 30, 2026

Advisory Details (1)

Auto-updated Jun 2, 2026
Patch available. Sources: github.
github Patch Available

Command injection via $TMUX environment variable leads to RCE as root · Advisory · mcdope/pam_usb · GitHub

https://github.com/mcdope/pam_usb/security/advisories/GHSA-822m-whrh-vrj8

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 51× 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 109 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-44713?
CVE-2026-44713 is a high vulnerability published on May 27, 2026. pam_usb provides hardware authentication for Linux using ordinary removable media. Prior to 0.8.7, src/tmux.c reads the user's $TMUX environment variable, splits it on commas, and interpolates the socket-path component directly into a shell command passed to popen(). Because the value is placed…
When was CVE-2026-44713 disclosed?
CVE-2026-44713 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on May 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44713 actively exploited?
CVE-2026-44713 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44713?
CVE-2026-44713 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-44713?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44713, 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-44713

Explore →

Is Your Infrastructure Affected by CVE-2026-44713?

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