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.
CVE-2026-90679
Score 4.3 from GitHub Security Advisory published 2026-09-13. a secondary CVSS source baseline 4.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- EG Score
- 4.3(high)
- EG Risk
- 19(Track)EG Risk 19/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity43% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 6%
- KEV
- Not listed
Published
September 13, 2026
Last Modified
September 15, 2026
Advisory Details (1)
Auto-updated Sep 13, 2026#14271 - bug: Experimental Security Issue: federation activity spoofing via unbound HTTP signature - forgejo/forgejo - Codeberg.org
https://codeberg.org/forgejo/forgejo/issues/14271#issuecomment-22548004Vendor Advisories for CVE-2026-90679(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 20× in last 7d / 20× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 18:35 UTCGHSA enrichment
- 2026-09-17 19:35 UTCEG score recompute
- 2026-09-17 19:35 UTCGHSA enrichment
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-16 17:58 UTCEG score recompute
- 2026-09-16 17:58 UTCGHSA enrichment
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 18:35 UTCEG score recompute
- 2026-09-15 18:35 UTCGHSA enrichment
- 2026-09-15 17:24 UTCEG score recompute
- 2026-09-15 17:24 UTCGHSA enrichment
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-15 03:10 UTCGHSA enrichment
- 2026-09-14 04:17 UTCEG score recompute
- 2026-09-14 04:17 UTCGHSA enrichment
- 2026-09-13 04:23 UTCEG score recompute
- 2026-09-13 04:02 UTCEG score recompute
- 2026-09-13 04:01 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-90679?
When was CVE-2026-90679 disclosed?
Is CVE-2026-90679 actively exploited?
What is the CVSS score of CVE-2026-90679?
How do I remediate CVE-2026-90679?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-90679
Is Your Infrastructure Affected by CVE-2026-90679?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.