{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42603 exists.","fix":"No fix has been published for CVE-2026-42603 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-42603 is a high-severity code injection vulnerability in OWASP-BLT BLT, published on 11 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-42603 and fix it if it is affected.\n\nWhat it is: CVE-2026-42603 is a high-severity code injection vulnerability in OWASP-BLT BLT, published on 11 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42603 exists.\n\nAffected product: OWASP-BLT BLT. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-42603/ (Markdown: https://insights.sbomify.com/CVE-2026-42603/index.md)","id":"CVE-2026-42603","markdown":"https://insights.sbomify.com/CVE-2026-42603/index.md","name":"CVE-2026-42603","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"QA testing platform","requires_auth":"none","summary":"Attackers can execute arbitrary code with write permissions by exploiting privileged GitHub Actions workflows that process untrusted fork code.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-95","name":"Improper Neutralization of Directives in Dynamically Evaluated Code"},{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"OWASP BLT is a QA testing and vulnerability disclosure platform that encompasses websites, apps, git repositories, and more. Prior to 2.1.2, .github/workflows/pre-commit-fix.yaml uses pull_request_target (privileged trigger) but checks out and executes code directly from the attacker's fork, enabling RCE with write permissions. This vulnerability is fixed in 2.1.2.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"OWASP BLT: pre-commit-fix.yaml executes untrusted fork code via pull_request_target","id":"CVE-2026-42603","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Actual has an OpenID `client_secret` Disclosure via Broken Authorization Guard in `/openid/config`","id":"CVE-2026-42604"},"packages":[],"prev":{"headline":"azureauthextension Authenticate method does not validate bearer tokens, allowing auth bypass via replay","id":"CVE-2026-42602"},"products":["BLT"],"published":"2026-05-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-11","vendors":["OWASP-BLT"]},"summary":"Attackers can execute arbitrary code with write permissions by exploiting privileged GitHub Actions workflows that process untrusted fork code.","url":"https://insights.sbomify.com/CVE-2026-42603/"}