{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119547 exists.","exposure":"","fix":"No fix has been published for CVE-2026-119547 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-119547 is a medium-severity vulnerability in forgejo, published on 30 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-119547 and fix it if it is affected.\n\nWhat it is: CVE-2026-119547 is a medium-severity vulnerability in forgejo, published on 30 Oct 2026. \nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119547 exists.\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-119547/ (Markdown: https://insights.sbomify.com/CVE-2026-119547/index.md)","id":"CVE-2026-119547","markdown":"https://insights.sbomify.com/CVE-2026-119547/index.md","name":"CVE-2026-119547","record":{"aliases":["GHSA-5fqg-pfrh-8fj8"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"Forgejo through 15.0.11, 16.0.0 through 16.0.7, and 17.0.0 through 17.0.1 contains an information disclosure vulnerability in the GetPublicKey API handler that lacks an ownership check on key lookups. Authenticated users with a read:user token or session can enumerate sequential key IDs to obtain titles, fingerprints and public key material of other users' SSH, deploy and principal keys.","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":"Forgejo through 15.0.11, 16.0.7, and 17.0.1 Information Disclosure via /api/v1/user/keys/{id}","id":"CVE-2026-119547","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Lago through 1.55.0 Cross-Organization Invoice Payment Manipulation via Stripe Webhook","id":"CVE-2026-119548"},"nickname":null,"packages":[],"prev":{"headline":"Forgejo through 15.0.11, 16.0.7, and 17.0.1 Path Traversal via restore-repo","id":"CVE-2026-119546"},"products":["forgejo"],"published":"2026-10-30","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":"partial"},"state":"PUBLISHED","updated":"2026-11-05","vendors":["forgejo"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-119547/"}