{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-66874 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-66874 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-66874 is a medium-severity vulnerability in Gitea, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-66874 and fix it if it is affected.\n\nWhat it is: CVE-2026-66874 is a medium-severity vulnerability in Gitea, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-66874 in the wild and no public exploit code.\n\nAffected product: Gitea. 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-66874/ (Markdown: https://insights.sbomify.com/CVE-2026-66874/index.md)","id":"CVE-2026-66874","markdown":"https://insights.sbomify.com/CVE-2026-66874/index.md","name":"CVE-2026-66874","record":{"aliases":["GHSA-5xp7-r6cr-39ff"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Gitea Git hosting","requires_auth":"low_privilege","summary":"Attackers can bypass required workflow checks in Gitea by submitting fork pull requests with skipped workflows, allowing unapproved code to merge.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Gitea","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-807","name":"Reliance on Untrusted Inputs in a Security Decision"},{"id":"CWE-693","name":"Protection Mechanism Failure"},{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"},{"id":"CWE-284","name":"Improper Access Control"}],"description":"For pull request events, Gitea reads workflow definitions from the pull request head and posts a synthetic skipped status when workflow branch or path filters exclude execution. A fork pull request author can supply a workflow matching a required status context but deliberately prevent it from running. Because skipped statuses count as success, branch protection or organization-required workflow checks can appear satisfied without the mandated workflow executing; no runner or maintainer approval is required for this path.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Gitea required Actions check bypass through skipped workflows","id":"CVE-2026-66874","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Mira Hormone Monitor, Mira Android App Missing authentication for critical function","id":"CVE-2026-66875"},"packages":[],"prev":{"headline":"Apache Thrift: c_glib multiplexed processor crashes on a message it cannot route","id":"CVE-2026-66859"},"products":["Gitea"],"published":"2026-10-14","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-14","vendors":["Gitea"]},"summary":"Attackers can bypass required workflow checks in Gitea by submitting fork pull requests with skipped workflows, allowing unapproved code to merge.","url":"https://insights.sbomify.com/CVE-2026-66874/"}