{"answers":{"affected":"1 open source package ship an affected version, including github.com/chrismellard/docker-credential-acr-env.","exploited":"There is no known exploitation of GO-2026-6225 in the wild and no public exploit code.","fix":"No fix has been published for GO-2026-6225 yet. Limit exposure of the affected software until one is available.","what":"GO-2026-6225 is a vulnerability in github.com/chrismellard/docker-credential-acr-env, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GO-2026-6225 and fix it if it is affected.\n\nWhat it is: GO-2026-6225 is a vulnerability in github.com/chrismellard/docker-credential-acr-env, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GO-2026-6225 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/chrismellard/docker-credential-acr-env (Go): affected all versions; no fix listed\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GO-2026-6225/ (Markdown: https://insights.sbomify.com/GO-2026-6225/index.md)","id":"GO-2026-6225","markdown":"https://insights.sbomify.com/GO-2026-6225/index.md","name":"GO-2026-6225","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Go credential helper","requires_auth":"none","summary":"An attacker can steal Azure AD access tokens by registering a malicious hostname containing .azurecr.io, exploiting an unanchored regex in the credential helper.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In github.com/chrismellard/docker-credential-acr-env/pkg/credhelper, the regular expression used by isACRRegistry to validate Azure Container Registry hostnames is unanchored. As a result, arbitrary hostnames containing the substring \".azurecr.io\" (such as evil.azurecr.io.attacker.com) are treated as valid ACR registries, causing ACRCredHelper.Get to send the Azure Active Directory (AAD) access token to attacker-controlled hosts.","ecosystems":["Go"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":false,"headline":"Credential leakage to untrusted hosts in github.com/chrismellard/docker-credential-acr-env","id":"GO-2026-6225","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Go","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":[],"package":"github.com/chrismellard/docker-credential-acr-env","purl":"pkg:golang/github.com/chrismellard/docker-credential-acr-env","source":"GO-2026-6225"}],"products":null,"published":"2026-08-18","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"An attacker can steal Azure AD access tokens by registering a malicious hostname containing .azurecr.io, exploiting an unanchored regex in the credential helper.","url":"https://insights.sbomify.com/GO-2026-6225/"}