CVE-2026-56657 json
Gitea SSH Key Parser Denial of Service
published 3mo ago modified last mo. also GHSA-4xjf-493q-98p3 , GO-2026-6042 , EUVD-2026-58144
- cvss
- 6.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 6%
- public exploits
- 0
- none known
Summary
Gitea SSH Key Parser Denial of Service
Patch / fix
- go code.gitea.io/gitea 1.27.0
- go gitea.dev 1.27.0
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
opensuse advisories openSUSE-SU-2026:21483-1
Is CVE-2026-56657 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-56657 updated cvss 6.5
code.gitea.io/gitea: Gitea: Denial of Service in SSH Key Parser
-
Red Hat OpenShift Pipelines openshift-pipelines-client, openshift-pipelines/pipelines-opc-rhel9, openshift-pipelines/pipelines-cli-tkn-rhel9, openshift-pipelines/pipelines-pipelines-as-code-cli-rhel9, openshift-pipelines/pipelines-pipelines-as-code-watcher-rhel9, openshift-pipelines/pipelines-pipelines-as-code-controller-rhel9not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2mo ago
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 6.2 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| CNA | 3.1 | 6.2 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 6.2 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | code.gitea.io/gitea | <1.27.0 |
1.27.0 |
| go | gitea.dev | <1.27.0 |
1.27.0 |
Affected products
- Gitea Gitea Open Source Git Server
Classification
References
-
github.com
/go-gitea/gitea/commit/de4b8277e9cb576f2315fb03b5ab6478b42a1d31
web
-
github.com
/go-gitea/gitea/security/advisories/GHSA-4xjf-493q-98p3
vendor-advisory, web, advisory
-
github.com
/go-gitea/gitea/releases/tag/v1.27.0
release-notes, web
-
blog.gitea.com
/gitea-1.27.0-is-released/
release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2026-56657
advisory
-
blog.gitea.com
/gitea-1.27.0-is-released
web
-
github.com
/go-gitea/gitea
package
Sources
- CVE List CVE-2026-56657
- GitHub Advisory GHSA-4xjf-493q-98p3
- NVD CVE-2026-56657
- OSV GO-2026-6042
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.