CVE-2026-45793Network attack vector

OAuth token disclosure via exception interpolation

Published Jul 15, 2026 · Updated Jul 15, 2026

Information disclosure in Composer 1.0 before 1.10.28, 2.0.0 before 2.2.28, and 2.3.0 before 2.9.8 lets attackers read tokens in CI logs. BaseIO::loadConfiguration() rejects tokens containing hyphens under an incomplete allowed-character regex, then embeds the rejected secret verbatim in an exception rendered to stderr. Reaching the disclosure requires a configured GitHub OAuth token in the modern hyphenated format and captured stderr; exposure is bounded by access to the resulting logs and the token's scope and lifetime.

CVSS severity7.5
High
EPSS probability1.02%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Information disclosure in Composer 1.0 before 1.10.28, 2.0.0 before 2.2.28, and 2.3.0 before 2.9.8 lets attackers read tokens in CI logs. BaseIO::loadConfiguration() rejects tokens containing hyphens under an incomplete allowed-character regex, then embeds the rejected secret verbatim in an exception rendered to stderr. Reaching the disclosure requires a configured GitHub OAuth token in the modern hyphenated format and captured stderr; exposure is bounded by access to the resulting logs and the token's scope and lifetime.

The record

CVE
CVE-2026-45793
Published
Jul 15, 2026
Updated
Jul 15, 2026
Vendor
Composer
Product
Composer
Classifications
CWE-200, T1552.001
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jul 15, 2026CVE publishedPublication date reported by the CVE source.
  2. Jul 15, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>= 1.0, < 1.10.28
  2. Affected versionversion=>= 2.0.0, < 2.2.28
  3. Affected versionversion=>= 2.3.0, < 2.9.8

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Composer · Composerversion=>= 1.0, < 1.10.28; version=>= 2.0.0, < 2.2.28; version=>= 2.3.0, < 2.9.8

Published CVSS scores

7.5GitHubCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-200Exposure of Sensitive Information to an Unauthorized Actor
T1552.001Unsecured Credentials: Credentials In Files

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo