VulnerabilityPublished 28 Jan 2025Updated 4 Nov 2026

CVE-2025-22865: Golang 1.10 · Using ParsePKCS1PrivateKey to parse a RSA key that is missing the CRT values would panic

Affects golang-1.10Source GCVE Database

Compare

Not known to be exploited · CVSS 7.5 High.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Jan 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 26.04 LTSgolang-1.23`pkg:deb/ubuntu/golang-1.23?arch=source&distro=resolute`Other threats	Affected =1.23.10-1	Fixed in–
Ubuntu 25.10golang-1.23`pkg:deb/ubuntu/golang-1.23?arch=source&distro=questing`Other threats	Affected =1.23.8-1 =1.23.10-1 =1.23.10-1ubuntu0.2	Fixed in–
Ubuntu 25.10golang-1.24`pkg:deb/ubuntu/golang-1.24?arch=source&distro=questing`Other threats	Affected 1.24.2-1 – 1.24.4-1ubuntu1 4 affected builds	Fixed in–
Ubuntu 24.04 LTSgolang-1.21`pkg:deb/ubuntu/golang-1.21?arch=source&distro=noble`Other threats	Affected 1.21.1-1 – 1.21.9-1ubuntu0.1 11 affected builds	Fixed in–
Ubuntu 24.04 LTSgolang-1.23`pkg:deb/ubuntu/golang-1.23?arch=source&distro=noble`Other threats	Affected =1.23.1-1~24.04 =1.23.1-1~24.04.1	Fixed in–
Ubuntu 24.04 LTSgolang-1.24`pkg:deb/ubuntu/golang-1.24?arch=source&distro=noble`Other threats	Affected =1.24.4-1ubuntu1~24.04.1 =1.24.4-1ubuntu1~24.04.2 =1.24.13-2~24.04.1	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is applied, avoid parsing RSA keys that may be missing CRT values or implement error handling to catch panics from this function.

Description

CVE-2025-22865 is a vulnerability in Golang 1.10 where using the ParsePKCS1PrivateKey function to parse an RSA key missing CRT values causes a panic during key validation. This can lead to denial of service due to application crashes when processing malformed RSA keys.

Impact

An attacker could cause a denial of service by triggering a panic in applications using the vulnerable ParsePKCS1PrivateKey function with specially crafted RSA keys missing CRT values. This results in application crashes, potentially disrupting services that rely on Golang's cryptographic parsing. There is no reported impact on integrity or availability beyond the panic, and no known exploitation in the wild.

Summary

The vulnerability occurs in Golang 1.10's ParsePKCS1PrivateKey function, which attempts to parse RSA private keys. If the RSA key lacks the Chinese Remainder Theorem (CRT) values, the function panics while verifying the key's well-formedness. This behavior can cause applications using this function to crash unexpectedly when handling such keys. The CVSS 3.1 score is 7.5 (high severity) with network attack vector, low attack complexity, no privileges required, no user interaction, and high confidentiality impact but no integrity or availability impact. No known exploits in the wild have been reported. The affected versions include multiple Ubuntu package versions of Golang 1.6 through 1.13.6.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2026, 21:53 UTC

Technical details

References

Community reviews

Related threats