Quick answers
- Is CVE-2026-119547 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119547 being exploited in the wild.
- How severe is CVE-2026-119547?
- Medium severity, with a CVSS score of 4.3, published 30 October 2026.
- Which products and versions are affected?
- Forgejo through 15.0.11, 16.0.0 through 16.0.7, 17.0.0 through 17.0.1.
- Is there a fix for CVE-2026-119547?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-119547 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-119547?
- Check whether you run Forgejo at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The GetPublicKey API handler in Forgejo loads public keys by numeric ID without verifying ownership, allowing any authenticated user with read:user scope to enumerate sequential key IDs. The handler returns key titles, fingerprints, and public key blobs for SSH, deploy, and principal keys belonging to other users. The IDOR is present in versions through 15.0.11, 16.0.0–16.0.7, and 17.0.0–17.0.1; the GPG key handler correctly restricts to the current user and 404s on foreign IDs, but the SSH/deploy key handler does not.
Affected products
- Forgejo Forgejo through 15.0.11, 16.0.0 through 16.0.7, 17.0.0 through 17.0.1
Timeline
- 2026-10-30: disclosed
- 2026-10-30: advisory