CVE-2026-55987

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 78% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cisa-adp, epss
Elevated
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

OAuth2 sign-in reactivates an administrator-deactivated account on auth sources without refresh tokens (incomplete fix of #38009)

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
52(Track*)
EG Risk 52/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 computed
Severity81% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

July 21, 2026

Last Modified

August 26, 2026

Advisory Details (1)

Auto-updated Aug 14, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

OAuth2 sign-in reactivates an administrator-deactivated account on auth sources without refresh tokens (incomplete fix of #38009) · Advisory · go-gitea/gitea · GitHub

https://github.com/go-gitea/gitea/security/advisories/GHSA-vrhc-jjfc-m3m3

Vendor Advisories for CVE-2026-55987(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 1 ecosystem)
Go(2)
PackageVulnerable rangeFixed inDependents
code.gitea.io/gitea—1.27.0—
gitea.dev—1.27.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 50× 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.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-11 08:55 UTCEG score recompute
  3. 2026-09-10 09:35 UTCEPSS rescore
  4. 2026-09-09 11:12 UTCEG score recompute
  5. 2026-09-08 22:01 UTCEPSS rescore
  6. 2026-09-07 22:30 UTCEG score recompute
  7. 2026-09-07 16:01 UTCEPSS rescore
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-05 19:50 UTCEG score recompute
  10. 2026-09-05 08:28 UTCEG score recompute
  11. 2026-09-04 05:07 UTCEPSS rescore
  12. 2026-09-02 14:12 UTCEPSS rescore
  13. 2026-09-02 00:55 UTCEG score recompute
  14. 2026-09-01 13:54 UTCEPSS rescore
  15. 2026-09-01 04:40 UTCEPSS rescore
  16. 2026-08-31 00:46 UTCEG score recompute
  17. 2026-08-30 19:17 UTCEPSS rescore
  18. 2026-08-30 02:10 UTCEG score recompute
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-28 21:41 UTCEPSS rescore
  21. 2026-08-27 21:17 UTCEG score recompute
  22. 2026-08-27 14:25 UTCEPSS rescore
  23. 2026-08-26 17:43 UTCEG score recompute
  24. 2026-08-26 14:46 UTCEPSS rescore
  25. 2026-08-26 00:52 UTCEG score recompute
Show 29 more
  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-24 15:06 UTCEG score recompute
  3. 2026-08-23 05:20 UTCEG score recompute
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-22 06:49 UTCEG score recompute
  6. 2026-08-21 23:49 UTCEPSS rescore
  7. 2026-08-21 08:19 UTCEG score recompute
  8. 2026-08-20 22:55 UTCEPSS rescore
  9. 2026-08-19 22:30 UTCEG score recompute
  10. 2026-08-19 17:04 UTCEPSS rescore
  11. 2026-08-18 19:27 UTCEG score recompute
  12. 2026-08-18 13:48 UTCEPSS rescore
  13. 2026-08-17 15:50 UTCEG score recompute
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-16 17:20 UTCEG score recompute
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 06:03 UTCEG score recompute
  18. 2026-08-16 02:14 UTCEPSS rescore
  19. 2026-08-15 07:34 UTCEG score recompute
  20. 2026-08-15 01:30 UTCEPSS rescore
  21. 2026-08-14 20:09 UTCEG score recompute▲ 8.10
  22. 2026-08-14 20:08 UTCMITRE cvelistV5CVSS v3 → 8.1 · severity → HIGH
  23. 2026-08-13 17:17 UTCNVD update
  24. 2026-08-13 17:04 UTCEG score recompute▼ 8.10
  25. 2026-08-13 17:01 UTCMITRE cvelistV5
  26. 2026-07-30 15:51 UTCEG score recompute
  27. 2026-07-26 21:16 UTCEG score recompute
  28. 2026-07-23 03:20 UTCEG score recompute
  29. 2026-07-21 21:19 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-55987?
CVE-2026-55987 is a high vulnerability published on July 21, 2026. OAuth2 sign-in reactivates an administrator-deactivated account on auth sources without refresh tokens (incomplete fix of #38009)
When was CVE-2026-55987 disclosed?
CVE-2026-55987 was first published in the National Vulnerability Database on July 21, 2026, with the most recent update on August 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55987 actively exploited?
CVE-2026-55987 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 78.1% of all scored CVEs.
What is the CVSS score of CVE-2026-55987?
CVE-2026-55987 has a CVSS v3.1 base score of 8.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-55987?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55987, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55987

Explore →

Is Your Infrastructure Affected by CVE-2026-55987?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs