CVE-2026-55986 json
Email Management API Bypasses ManageCredentials Feature Restrictions
published 3mo ago modified 2mo ago also EUVD-2026-58140 , GHSA-46c7-w5w4-h644
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository go-gitea/gitea. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 25%
- public exploits
- 0
- none known
Summary
Email Management API Bypasses ManageCredentials Feature Restrictions
Patch / fix
Is CVE-2026-55986 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2mo ago
Exploit prediction
0.32% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/go-gitea/gitea/security/advisories/GHSA-46c7-w5w4-h644 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N |
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N |
Affected products
- Gitea Gitea Open Source Git Server
Classification
- Weakness
-
- CWE-284 Improper Access Control
References
-
github.com
/go-gitea/gitea/security/advisories/GHSA-46c7-w5w4-h644
vendor-advisory, exploit, advisory
-
github.com
/go-gitea/gitea/releases/tag/v1.27.0
release-notes
-
blog.gitea.com
/gitea-1.27.0-is-released/
release-notes
Sources
- CVE List CVE-2026-55986
- NVD CVE-2026-55986
- Maintainer advisory GHSA-46c7-w5w4-h644
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of go-gitea/gitea published their own advisory on GitHub. Reviewed sources take precedence over it.