# CVE-2026-49349: regclient may leak authentication credentials to external blob stores

> regclient may leak registry credentials to external servers when interacting with malicious registries or unrestricted blob stores.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 12 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-qvqc-4c52-x6qp, GO-2026-5822, MINI-2mxc-vg96-38hg, MINI-3rp9-ccjq-4v2r, MINI-cp6r-h56m-85wr, MINI-f284-3m5p-wm73, MINI-rr74-8p5r-rp2c

## What is CVE-2026-49349?

CVE-2026-49349 is a medium-severity vulnerability in regclient, published on 12 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

regclient is a Docker and OCI Registry Client in Go. Prior to version 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. Version 0.11.5 fixes the issue.

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2026-49349?

3 open source packages ship an affected version, including github.com/regclient/regclient.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/regclient/regclient` | Go | All versions | 0.11.5 |
| `github.com/regclient/regclient` | Go | All versions | 0.11.5 |
| `github.com/regclient/regclient` | Go | All versions | 0.11.5 |

## How do I fix CVE-2026-49349?

Upgrade github.com/regclient/regclient to 0.11.5 or later.

## Is CVE-2026-49349 being exploited?

There is no known exploitation of CVE-2026-49349 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-49349 and fix it if it is affected.

What it is: CVE-2026-49349 is a medium-severity vulnerability in regclient, published on 12 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-49349 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/regclient/regclient (Go): affected all versions; fixed in 0.11.5
- github.com/regclient/regclient (Go): affected all versions; fixed in 0.11.5
- github.com/regclient/regclient (Go): affected all versions; fixed in 0.11.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-49349/ (Markdown: https://insights.sbomify.com/CVE-2026-49349/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-49349
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-49349
- OSV: https://osv.dev/vulnerability/CVE-2026-49349

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-49349/
Summaries are generated and may contain mistakes; the official description above is the record.