# github.com/containers/image allows unexpected authenticated registry accesses Advisory record · `GHSA-6wvf-f2vw-3425` - **Identifiers:** `GHSA-6wvf-f2vw-3425` · `CVE-2024-3727` · `GO-2024-2842` - **State:** Confirmed - **Severity:** CVSS 8.3 High - **Critical:** No - **Weakness (CWE):** [CWE-354](https://cwe.mitre.org/data/definitions/354.html) - **Tags:** [CWE-354](https://agentprime.io/advisories/tag/cwe-354.md) - **Published:** 14 May 2024 - **Updated:** 10 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 14 May 2024, 18:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `github.com/containers/image` (Go): affected `<5.30.1`; fixed in `5.30.1` - `github.com/containers/image/v5` (Go): affected `>=5.30.0, <5.30.1 || <5.29.3`; fixed in `5.30.1`, `5.29.3` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > The Go library github.com/containers/image is vulnerable in versions before 5.30.1, and github.com/containers/image/v5 is vulnerable in versions before 5.29.3 and from 5.30.0 up to 5.30.1. An attacker can trigger unexpected authenticated registry accesses on behalf of a victim user, which can lead to resource exhaustion and local path traversal. The source gives few details on the exact conditions required. Upgrade to version 5.30.1 of github.com/containers/image, or to 5.29.3 or 5.30.1 of github.com/containers/image/v5. Written 2 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 8.3 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H`, from CNA (redhat) - **CISA KEV:** Not listed. - **EPSS:** 0.013, the 70th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 9 May 2024, 14:57 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2024-3727) - 14 May 2024, 15:42 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2024-3727) - 31 Oct 2026, 14:15 UTC: First seen by agentprime - 31 Oct 2026, 14:15 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-6wvf-f2vw-3425) ## Sources - [GitHub Advisory Database: GHSA-6wvf-f2vw-3425](https://github.com/advisories/GHSA-6wvf-f2vw-3425) - [OSV: GHSA-6wvf-f2vw-3425](https://osv.dev/vulnerability/GHSA-6wvf-f2vw-3425) - - - - - - - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .