CVE-2026-49349 is a medium-severity security vulnerability in github.com/regclient/regclient (go), affecting versions <= 0.11.4. It is fixed in 0.11.5.
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: 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
CVE-2026-49349 has a CVSS score of 6.8 (Medium). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (0.11.5). Upgrading removes the vulnerable code path.
go
github.com/regclient/regclient (<= 0.11.4)github.com/regclient/regclient → 0.11.5 (go)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2026-49349 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-49349 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-49349 in your environment →Upgrade github.com/regclient/regclient to 0.11.5 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-49349 is a medium-severity security vulnerability in github.com/regclient/regclient (go), affecting versions <= 0.11.4. It is fixed in 0.11.5.
CVE-2026-49349 has a CVSS score of 6.8 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
github.com/regclient/regclient (go) versions <= 0.11.4 is affected.
Yes. CVE-2026-49349 is fixed in 0.11.5. Upgrade to this version or later.
Whether CVE-2026-49349 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
Upgrade github.com/regclient/regclient to 0.11.5 or later.