{"answers":{"affected":"3 open source packages ship an affected version, including github.com/russellhaering/goxmldsig. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33487 exists.","fix":"Upgrade github.com/russellhaering/goxmldsig to 1.6.0 or later.","what":"CVE-2026-33487 is a high-severity vulnerability in russellhaering goxmldsig, published on 26 Mar 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-33487 and fix it if it is affected.\n\nWhat it is: CVE-2026-33487 is a high-severity vulnerability in russellhaering goxmldsig, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33487 exists.\n\nAffected packages and fixed versions:\n- github.com/russellhaering/goxmldsig (Go): affected all versions; fixed in 1.6.0\n- github.com/russellhaering/goxmldsig (Go): affected all versions; fixed in 1.6.0\n- github.com/russellhaering/goxmldsig (Go): affected all versions; fixed in 1.6.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-33487/ (Markdown: https://insights.sbomify.com/CVE-2026-33487/index.md)","id":"CVE-2026-33487","markdown":"https://insights.sbomify.com/CVE-2026-33487/index.md","name":"CVE-2026-33487","record":{"aliases":["CLEANSTART-2026-TW34089","CLEANSTART-2026-VA24082","CLEANSTART-2026-WK71249","GHSA-479m-364c-43vc","GO-2026-4753","MINI-2h4j-p74g-qr9p","MINI-35rh-257w-3rgx","MINI-446w-6v3c-rv67","MINI-62mf-h9q4-7m9c","MINI-66m6-7gwr-h6hp","MINI-6j5f-2p48-5h24","MINI-75jx-x4w5-7v97","MINI-7gh4-ff93-m429","MINI-7w27-m868-32vj","MINI-8wfh-rgmw-gp6x","MINI-95f7-7hhq-cv3f","MINI-9qpr-82gc-9wjf","MINI-ccf6-594f-c857","MINI-crrw-fvcw-xjfm","MINI-f8xw-rw74-6fg9","MINI-fj69-8pg9-6p45","MINI-gcc6-3372-wgqf","MINI-h8rc-fx3v-2j4r","MINI-hv8j-234p-85gc","MINI-jj45-h9rx-3p3h","MINI-mrgc-367w-wx2x","MINI-wc4h-3fc6-hrxc","MINI-xx72-wm4v-5f5c","MINI-xxcr-9rf2-8m54","ROOT-APP-GOBINARY-CVE-2026-33487"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Go XML signature library","requires_auth":"none","summary":"Attackers can bypass XML digital signature validation in goxmldsig due to a loop variable capture bug, allowing forged signatures to be accepted.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"goxmldsig","vendor":"goxmldsig_project"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-682","name":"Incorrect Calculation"},{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"goxmlsig provides XML Digital Signatures implemented in Go. Prior to version 1.6.0, the `validateSignature` function in `validate.go` goes through the references in the `SignedInfo` block to find one that matches the signed element's ID. In Go versions before 1.22, or when `go.mod` uses an older version, there is a loop variable capture issue. The code takes the address of the loop variable `_ref` instead of its value. As a result, if more than one reference matches the ID or if the loop logic is incorrect, the `ref` pointer will always end up pointing to the last element in the `SignedInfo.References` slice after the loop. goxmlsig version 1.6.0 contains a patch.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"goxmldsig has validateSignature Loop Variable Capture Signature Bypass","id":"CVE-2026-33487","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":"AVideo has a PGP 2FA Bypass via Cryptographically Broken 512-bit RSA Key Generation in LoginControl Plugin","id":"CVE-2026-33488"},"packages":[{"ecosystem":"Go","fixed":["1.6.0"],"introduced":["0"],"last_affected":[],"package":"github.com/russellhaering/goxmldsig","purl":null,"source":"GHSA-479m-364c-43vc"},{"ecosystem":"Go","fixed":["1.6.0"],"introduced":["0"],"last_affected":[],"package":"github.com/russellhaering/goxmldsig","purl":"pkg:golang/github.com/russellhaering/goxmldsig","source":"GHSA-479m-364c-43vc"},{"ecosystem":"Go","fixed":["1.6.0"],"introduced":["0"],"last_affected":[],"package":"github.com/russellhaering/goxmldsig","purl":"pkg:golang/github.com/russellhaering/goxmldsig","source":"GO-2026-4753"}],"prev":{"headline":"Roadiz has Server-Side Request Forgery (SSRF) in roadiz/documents","id":"CVE-2026-33486"},"products":["goxmldsig"],"published":"2026-03-26","related":[{"cvss_score":7.5,"headline":"Denial of Service (DoS)","id":"CVE-2020-7711","kev_date_added":null,"published":"2020-08-23"}],"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-09","vendors":["russellhaering"]},"summary":"Attackers can bypass XML digital signature validation in goxmldsig due to a loop variable capture bug, allowing forged signatures to be accepted.","url":"https://insights.sbomify.com/CVE-2026-33487/"}