{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90679 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-90679 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-90679 is a medium-severity authentication bypass vulnerability in Forgejo, published on 13 Sep 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-90679 and fix it if it is affected.\n\nWhat it is: CVE-2026-90679 is a medium-severity authentication bypass vulnerability in Forgejo, published on 13 Sep 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-90679 in the wild and no public exploit code.\n\nAffected product: Forgejo. 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-90679/ (Markdown: https://insights.sbomify.com/CVE-2026-90679/index.md)","id":"CVE-2026-90679","markdown":"https://insights.sbomify.com/CVE-2026-90679/index.md","name":"CVE-2026-90679","record":{"aliases":["GHSA-5cjj-j77f-rq2g"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Forgejo Git platform","requires_auth":"low_privilege","summary":"Remote attackers can spoof ActivityPub identities in Forgejo when federation is enabled, bypassing signature verification to attribute actions to arbitrary actors.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-348","name":"Use of Less Trusted Source"}],"description":"Forgejo 13.0.0 through 16.0.4, when \"[federation] ENABLED = true\" is set, has a spoofing issue that affects identity integrity but does not allow account takeover or content modification. It does not verify that the HTTP Signature on an incoming ActivityPub activity was produced by the key belonging to the actor named in the activity body. The signature verification in routers/api/v1/activitypub/reqsignature.go validates the request signature, but the inbox activity handlers subsequently read the acting identity from the attacker-controlled JSON body without binding it to the verified signing key. Additionally, the signed Digest header is not recomputed against the received request body. A remote attacker who hosts a single valid ActivityPub actor and keypair can therefore submit signature-valid activities attributed to any actor identity they name.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Auth bypass in Forgejo","id":"CVE-2026-90679","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"D-Link DIR-823G HNAP1 SetStaticRouteSettings strcpy stack-based overflow","id":"CVE-2026-90680"},"packages":[],"prev":{"headline":"Other in HAProxy","id":"CVE-2026-90678"},"products":["Forgejo"],"published":"2026-09-13","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-09-15","vendors":["Forgejo"]},"summary":"Remote attackers can spoof ActivityPub identities in Forgejo when federation is enabled, bypassing signature verification to attribute actions to arbitrary actors.","url":"https://insights.sbomify.com/CVE-2026-90679/"}