CVE-2026-92390VulnerabilityPublished 14 Oct 2026Updated 3 Nov 2026

When invoked with --remote-header-name (-J), curl fails to preserve its documented anti-clobbering protection if an

Affects curlSource GCVE Database

Compare

Authoritative record:CVE-2026-92390· High 7.5

Not known to be exploited · CVSS 7.5 High · fixed in 8.20.0-2ubuntu11.1 : patch curl soon.

Data as of 3 Nov 2026, 23:49 UTC

CVSS 3.1 base score

7.5High

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

Thin evidence

One scorer or none

CVSS scores by source
CISA-ADP	CVSS 3.1	7.5

Patch: Available – fixed in 8.20.0-2ubuntu11.1, 8.18.0-1ubuntu2.8

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
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: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 20 Oct 2026
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 3 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

Upgrade the Ubuntu curl to 8.20.0-2ubuntu11.1 (package) or 8.18.0-1ubuntu2.8 (package).

Patches and advisories

Affected software

Product	Affected	Fixed in
Ubuntu 26.10curl`pkg:deb/ubuntu/curl?arch=source&distro=stonking`Other threats	Affected <8.20.0-2ubuntu11.1	Fixed in 8.20.0-2ubuntu11.1
Ubuntu 26.04 LTScurl`pkg:deb/ubuntu/curl?arch=source&distro=resolute`Other threats	Affected <8.18.0-1ubuntu2.8	Fixed in 8.18.0-1ubuntu2.8
Ubuntu Pro 20.04 LTScurl`pkg:deb/ubuntu/curl?arch=source&distro=esm-infra/focal`Other threats	Affected 7.65.3-1ubuntu3 – 7.68.0-1ubuntu2.25+esm10 35 affected builds	Fixed in–
Ubuntu Pro 18.04 LTScurl`pkg:deb/ubuntu/curl?arch=source&distro=esm-infra/bionic`Other threats	Affected 7.55.1-1ubuntu2 – 7.58.0-2ubuntu3.24+esm15 41 affected builds	Fixed in–
Ubuntu Pro 16.04 LTScurl`pkg:deb/ubuntu/curl?arch=source&distro=esm-infra-legacy/xenial`Other threats	Affected 7.43.0-1ubuntu2 – 7.47.0-1ubuntu2.19+esm21 41 affected builds	Fixed in–
Ubuntu Pro 14.04 LTScurl`pkg:deb/ubuntu/curl?arch=source&distro=esm-infra-legacy/trusty`Other threats	Affected 7.32.0-1ubuntu1 – 7.35.0-1ubuntu2.20+esm24 46 affected builds	Fixed in–

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

AI-suggested

A patch is available and should be applied. The issue is fixed in curl versions 8.20.0-2ubuntu11.1 and 8.18.0-1ubuntu2.8 as per the Ubuntu security advisory USN-8927-1. Users should upgrade to these or later versions to mitigate the vulnerability. No additional mitigation steps are indicated by the vendor advisory.

Description

A vulnerability in curl occurs when using the --remote-header-name (-J) option. If an intermediate 103 Early Hints HTTP response precedes the final response, or if an ETag header is processed before Content-Disposition under --etag-save, curl fails to enforce its anti-clobbering protection. This allows an HTTP(S) server to overwrite an existing local file despite the -J option's non-overwrite intent. The issue affects multiple versions of curl and has been fixed in specific Ubuntu package releases.

Impact

An attacker controlling an HTTP(S) server can exploit this vulnerability to overwrite existing local files on a client system when curl is used with the -J option. This could lead to unauthorized modification of local files, potentially impacting system integrity or security. The CVSS score of 7.5 (high severity) reflects the potential for high impact on integrity without requiring privileges or user interaction.

References

Community reviews

Loading reviews…