{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-123638 in the wild and no public exploit code.","exposure":"Only installations with a non-default setting turned on are exposed.","fix":"No fix has been published for CVE-2026-123638 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-123638 is a high-severity security feature bypass vulnerability in Gitea, published on 15 Nov 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-123638 and fix it if it is affected.\n\nWhat it is: CVE-2026-123638 is a high-severity security feature bypass vulnerability in Gitea, published on 15 Nov 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-123638 in the wild and no public exploit code.\nExposure: Only installations with a non-default setting turned on are exposed.\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-123638/ (Markdown: https://insights.sbomify.com/CVE-2026-123638/index.md)","id":"CVE-2026-123638","markdown":"https://insights.sbomify.com/CVE-2026-123638/index.md","name":"CVE-2026-123638","record":{"aliases":["GHSA-w87g-xmrp-86v2"],"analysis":{"component_type":"developer_tool","exploitable_when_present":false,"fix_type":"upgrade","impacts":["security_bypass","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Git hosting service","requires_auth":"low_privilege","requires_specific_call":false,"summary":"Users with write access can bypass Gitea branch protection patterns using quoted file names to modify protected files or run workflows.","user_interaction":"not_required","vuln_class":"security_feature_bypass","vulnerable_functions":[]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"Gitea","component":null,"cpe":[],"cvss":{"score":8.3,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-693","name":"Protection Mechanism Failure"}],"description":"The \"Protected file patterns\" setting of a branch protection rule was checked against file names as git prints them, and git quotes names that contain a double quote, a backslash or a control character. Such names never matched a pattern, so a user with write access could add or change files under a protected pattern by direct push or through a pull request merge, and could move a protected file out of the pattern's reach by renaming it. Where the patterns protect workflow files, this allowed adding a workflow that then ran on the repository's runners. Changed files are now listed unquoted, and a rename reports both the old and the new 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 protected file pattern bypass with quoted file names","id":"CVE-2026-123638","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"main_cpe":null,"main_fixed":[],"main_package":null,"n_packages":0,"n_references":4,"n_vendor_status":0,"next":{"headline":"NGINX ngx_stream_ssl_preread_module vulnerability","id":"CVE-2026-123640"},"nickname":null,"packages":[],"prev":{"headline":"BIG-IP APM Vulnerability","id":"CVE-2026-123637"},"products":["Gitea"],"published":"2026-11-15","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","text_fixes":[],"updated":"2026-11-16","vendor_status":[],"vendors":["Gitea"]},"summary":"Users with write access can bypass Gitea branch protection patterns using quoted file names to modify protected files or run workflows.","url":"https://insights.sbomify.com/CVE-2026-123638/"}