Vulnerability from bitnami_vulndb
When Gitea's built-in SSH server is enabled (START_SSH_SERVER = true), the presented public key was looked up with an SQL LIKE comparison of its encoded content, which is case-insensitive on some databases, including the default SQLite. An attacker who can construct a case variant of another user's registered RSA public key for which they can derive the private key could have that key matched to the victim's account and authenticate over SSH as that user. Keys are now looked up by fingerprint.
{
"affected": [
{
"package": {
"ecosystem": "Bitnami",
"name": "gitea",
"purl": "pkg:bitnami/gitea"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "28.0.0"
}
],
"type": "SEMVER"
}
],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
}
]
}
],
"aliases": [
"CVE-2026-103059"
],
"database_specific": {
"cpes": [
"cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*"
],
"severity": "Critical"
},
"details": "When Gitea\u0027s built-in SSH server is enabled (`START_SSH_SERVER = true`), the presented public key was looked up with an SQL `LIKE` comparison of its encoded content, which is case-insensitive on some databases, including the default SQLite. An attacker who can construct a case variant of another user\u0027s registered RSA public key for which they can derive the private key could have that key matched to the victim\u0027s account and authenticate over SSH as that user. Keys are now looked up by fingerprint.",
"id": "BIT-gitea-2026-103059",
"modified": "2026-10-16T09:07:50.945Z",
"published": "2026-10-16T08:36:29.274Z",
"references": [
{
"type": "ARTICLE",
"url": "https://blog.gitea.com/release-of-28.0.0/"
},
{
"type": "FIX",
"url": "https://github.com/go-gitea/gitea/pull/39423"
},
{
"type": "ARTICLE",
"url": "https://github.com/go-gitea/gitea/releases/tag/v28.0.0"
},
{
"type": "ADVISORY",
"url": "https://github.com/go-gitea/gitea/security/advisories/GHSA-8pwg-hcgm-54cp"
},
{
"type": "WEB",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-103059"
}
],
"schema_version": "1.6.2",
"summary": "Gitea built-in SSH server authentication bypass through key case folding"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.