{"answers":{"affected":"3 open source packages ship an affected version, including github.com/elastic/package-registry. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-33467 in the wild and no public exploit code.","fix":"Upgrade github.com/elastic/package-registry to 1.38.0 or later.","what":"CVE-2026-33467 is a medium-severity vulnerability in Elastic Package Registry, published on 28 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-33467 and fix it if it is affected.\n\nWhat it is: CVE-2026-33467 is a medium-severity vulnerability in Elastic Package Registry, published on 28 Apr 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 CVE-2026-33467 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/elastic/package-registry (Go): affected all versions; fixed in 1.38.0\n- github.com/elastic/package-registry (Go): affected all versions; fixed in 1.38.0\n- github.com/elastic/package-registry (Go): affected all versions; fixed in 1.38.0\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/CVE-2026-33467/ (Markdown: https://insights.sbomify.com/CVE-2026-33467/index.md)","id":"CVE-2026-33467","markdown":"https://insights.sbomify.com/CVE-2026-33467/index.md","name":"CVE-2026-33467","record":{"aliases":["GHSA-r727-5pf6-47r2","GO-2026-5611"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Elastic Package Registry","requires_auth":"none","summary":"Attackers can bypass integrity checks to install tampered packages in Elastic Package Registry, potentially leading to code execution.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"elastic_package_registry","vendor":"elastic"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"Improper Verification of Cryptographic Signature (CWE-347) in Elastic Package Registry could allow an attacker positioned to intercept network traffic, or to otherwise influence the contents served to a self-hosted registry, to substitute a tampered package without the integrity check failing closed.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Improper Verification of Cryptographic Signature in Elastic Package Registry Leading to Package Integrity Bypass","id":"CVE-2026-33467","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"Kysely has a MySQL SQL Injection via Insufficient Backslash Escaping in `sql.lit(string)` usage or similar methods that append string literal values into the compiled SQL strings","id":"CVE-2026-33468"},"packages":[{"ecosystem":"Go","fixed":["1.38.0"],"introduced":["0"],"last_affected":[],"package":"github.com/elastic/package-registry","purl":null,"source":"GHSA-r727-5pf6-47r2"},{"ecosystem":"Go","fixed":["1.38.0"],"introduced":["0"],"last_affected":[],"package":"github.com/elastic/package-registry","purl":"pkg:golang/github.com/elastic/package-registry","source":"GHSA-r727-5pf6-47r2"},{"ecosystem":"Go","fixed":["1.38.0"],"introduced":["0"],"last_affected":[],"package":"github.com/elastic/package-registry","purl":"pkg:golang/github.com/elastic/package-registry","source":"GO-2026-5611"}],"prev":{"headline":"Improper Limitation of a Pathname to a Restricted Directory in Logstash Leading to Arbitrary File Write","id":"CVE-2026-33466"},"products":["Elastic Package Registry"],"published":"2026-04-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-29","vendors":["Elastic"]},"summary":"Attackers can bypass integrity checks to install tampered packages in Elastic Package Registry, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2026-33467/"}