Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

BIT-composer-2026-59947: Composer: URL-embedded HTTP-Basic username leaks to verbose logs (GitHub PAT exposure)

0
Medium
Published: 07/14/2026 (07/14/2026, 08:40:59 UTC)
Source: GCVE Database
Product: composer

Description

Composer versions prior to 2.2.29 and 2.10.2 may leak HTTP Basic authentication credentials embedded in URLs to verbose debug logs when run with -vvv verbosity. This includes sensitive tokens such as GitHub Personal Access Tokens in the username portion of repository or package URLs. The issue arises because certain components did not sanitize username-only credentials in URLs before logging. Fixed versions 2.2.29 and 2.10.2 address this by properly sanitizing such credentials in debug output.

Affected software

Bitnamimore threats →ghsa
composer
pkg:bitnami/composer
Affected versions
>=1.0.0 <2.2.29>=2.3.0 <2.10.2

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 07/14/2026, 11:32:55 UTC

Technical Analysis

Composer, a PHP dependency manager, had a vulnerability (CVE-2026-59947) where running Composer with maximum debug verbosity (-vvv) could expose credentials embedded in the username field of URLs (e.g., https://TOKEN@host/) in verbose logs. This occurred because the AuthHelper, Url::sanitize, and ProcessExecutor components did not sanitize username-only URL credentials before logging. This could lead to exposure of sensitive tokens such as GitHub Personal Access Tokens. The vulnerability affects Composer versions >=1.0.0 <2.2.29 and >=2.3.0 <2.10.2 and was fixed in versions 2.2.29 and 2.10.2.

Potential Impact

Sensitive credentials embedded in URLs, such as GitHub Personal Access Tokens, could be exposed in verbose debug logs when running affected Composer versions with -vvv verbosity. This exposure could lead to unauthorized access if logs are accessible to attackers or unauthorized users. There are no known exploits in the wild reported for this vulnerability.

Mitigation Recommendations

Upgrade Composer to version 2.2.29 or later, or 2.10.2 or later, where this issue is fixed. Avoid running Composer with -vvv verbosity in environments where logs may be exposed until upgraded. Patch status is confirmed fixed in these versions.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
BIT-composer-2026-59947
Osv Schema Version
1.6.2
Aliases
["CVE-2026-59947"]
Ecosystems
["Bitnami"]
Database Specific Severity
Medium
Cvss Version
null

Threat ID: 6a561c4a68715ace4365a304

Added to database: 07/14/2026, 11:23:54 UTC

Last enriched: 07/14/2026, 11:32:55 UTC

Last updated: 07/14/2026, 11:32:55 UTC

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses