CVE-2026-45793

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.8%, top 47% 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: epss, secondary
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

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

Composer is a dependency Manager for the PHP language. Prior to 1.10.28, 2.2.28, and 2.9.8, Composer\IO\BaseIO::loadConfiguration() validates GitHub OAuth tokens with the regex ^[.A-Za-z0-9_]+$ and interpolates rejected tokens into an UnexpectedValueException; GitHub Actions GITHUB_TOKEN values using the ghs__ format can contain -, fail validation, and be disclosed to stderr or CI logs. This issue is fixed in versions 1.10.28, 2.2.28, and 2.9.8.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
53%
KEV
Not listed

Published

May 19, 2026

Last Modified

July 15, 2026

Advisory Details (9)

Auto-updated Jul 15, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

2.9.8

Patch available: composer/composer 2.9.8

https://github.com/composer/composer/releases/tag/2.9.8
github_release Patch Available

2.2.28

Patch available: composer/composer 2.2.28

https://github.com/composer/composer/releases/tag/2.2.28
github_release Patch Available

1.10.28

Patch available: composer/composer 1.10.28

https://github.com/composer/composer/releases/tag/1.10.28
github_commit Patch Available

commit e66c8fdb7ff5 (composer/composer)

Patch available: composer/composer 1.10.28 (contains commit e66c8fdb7ff5)

https://github.com/composer/composer/commit/e66c8fdb7ff5409bd2f358c5f194038e49e93714
github_commit Patch Available

commit 65e6390c49f1 (composer/composer)

Patch available: composer/composer 2.2.28 (contains commit 65e6390c49f1)

https://github.com/composer/composer/commit/65e6390c49f1a11cd8b660d81822086db51fe2d1
github_commit Patch Available

commit 3f5e7f9fbfa5 (composer/composer)

Patch available: composer/composer 2.9.8 (contains commit 3f5e7f9fbfa5)

https://github.com/composer/composer/commit/3f5e7f9fbfa541137d6d1d5643ec3b718e9d5039
github_pr Patch Available

Fix regexp for new GitHub installation tokens (1.10)

Patch available: composer/composer 1.10.28 (PR #12855 merged 2026-05-13)

https://github.com/composer/composer/pull/12855
github_pr Patch Available

Fix regexp for new GitHub installation tokens

Patch available: composer/composer 2.9.8 (PR #12853 merged 2026-05-13)

https://github.com/composer/composer/pull/12853
github Patch Available

Github Actions issued GITHUB_TOKEN disclosure in GitHub Actions logs · Advisory · composer/composer · GitHub

https://github.com/composer/composer/security/advisories/GHSA-f9f8-rm49-7jv2

Vendor Advisories for CVE-2026-45793(1)

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

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
composer2.0.11-1 ... 2.9.8-1 (96 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
composer2.5.5-1, 2.5.5-1+deb12u1, 2.5.5-1+deb12u2, 2.5.5-1+deb12u3, 2.5.5-1+deb12u42.5.5-1+deb12u5—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
composer2.8.8-1, 2.8.8-1+deb13u1, 2.8.8-1+deb13u22.8.8-1+deb13u3—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
composer2.10.0~rc1-1 ... 2.9.8-1 (18 versions)2.10.0-1—
Packagist(1)
PackageVulnerable rangeFixed inDependents
composer/composer1.0.0 ... 1.9.3 (96 versions)1.10.28—

Weakness Classification(1)

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

Data Freshness Timeline

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

  1. 2026-08-15 01:37 UTCEG score recompute
  2. 2026-08-15 01:30 UTCEPSS rescore
  3. 2026-08-14 02:06 UTCEG score recompute
  4. 2026-08-13 22:00 UTCEPSS rescore
  5. 2026-08-12 14:22 UTCEG score recompute
  6. 2026-08-12 13:51 UTCEPSS rescore
  7. 2026-08-11 13:53 UTCEG score recompute
  8. 2026-08-11 00:39 UTCEG score recompute
  9. 2026-08-11 00:00 UTCEPSS rescore
  10. 2026-08-10 01:07 UTCEG score recompute
  11. 2026-08-09 13:46 UTCEPSS rescore
  12. 2026-08-09 01:35 UTCEG score recompute
  13. 2026-08-08 16:37 UTCEPSS rescore
  14. 2026-08-07 20:25 UTCEG score recompute
  15. 2026-08-06 20:53 UTCEG score recompute
  16. 2026-08-06 13:47 UTCEPSS rescore
  17. 2026-08-05 21:21 UTCEG score recompute
  18. 2026-08-05 19:17 UTCEPSS rescore
  19. 2026-08-04 15:10 UTCEPSS rescore
  20. 2026-08-04 10:39 UTCEPSS rescore
  21. 2026-08-03 16:58 UTCEG score recompute
  22. 2026-08-03 10:36 UTCEPSS rescore
  23. 2026-08-02 05:40 UTCEG score recompute
  24. 2026-08-02 02:27 UTCEPSS rescore
  25. 2026-08-01 17:54 UTCEG score recompute
Show 23 more
  1. 2026-08-01 04:16 UTCEPSS rescore
  2. 2026-07-30 16:28 UTCEPSS rescore
  3. 2026-07-30 01:30 UTCEPSS rescore
  4. 2026-07-28 15:36 UTCEPSS rescore
  5. 2026-07-27 14:13 UTCEPSS rescore
  6. 2026-07-26 14:54 UTCEPSS rescore
  7. 2026-07-26 14:54 UTCEPSS rescore
  8. 2026-07-25 14:18 UTCEPSS rescore
  9. 2026-07-24 14:17 UTCEPSS rescore
  10. 2026-07-23 14:18 UTCEPSS rescore
  11. 2026-07-23 03:16 UTCEG score recompute
  12. 2026-07-22 14:08 UTCEPSS rescore
  13. 2026-07-21 15:24 UTCEPSS rescore
  14. 2026-07-20 17:08 UTCEPSS rescore
  15. 2026-07-19 14:31 UTCEPSS rescore
  16. 2026-07-19 02:29 UTCEPSS rescore
  17. 2026-07-18 10:04 UTCEPSS rescore
  18. 2026-07-17 23:29 UTCOSV refresh
  19. 2026-07-16 17:03 UTCEPSS rescore
  20. 2026-06-14 23:18 UTCEPSS rescore
  21. 2026-06-13 23:00 UTCEPSS rescore
  22. 2026-06-12 23:12 UTCEPSS rescore
  23. 2026-05-24 06:13 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-45793?
CVE-2026-45793 is a high vulnerability published on May 19, 2026. Composer is a dependency Manager for the PHP language. Prior to 1.10.28, 2.2.28, and 2.9.8, Composer\IO\BaseIO::loadConfiguration() validates GitHub OAuth tokens with the regex ^[.A-Za-z0-9]+$ and interpolates rejected tokens into an UnexpectedValueException; GitHub Actions GITHUBTOKEN values using…
When was CVE-2026-45793 disclosed?
CVE-2026-45793 was first published in the National Vulnerability Database on May 19, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45793 actively exploited?
CVE-2026-45793 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 46.7% of all scored CVEs.
What is the CVSS score of CVE-2026-45793?
CVE-2026-45793 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-45793?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45793, 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-45793

Explore →

Is Your Infrastructure Affected by CVE-2026-45793?

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

Start Free Scan →Browse All CVEs