CVE-2026-92390: -J no-clobber guarantee bypassed with 103 early hints

Published Oct 14, 2026
·
Updated

-J no-clobber guarantee bypassed with 103 early hints

Other sources

When invoked with --remote-header-name (-J), curl fails to preserve its documented anti-clobbering protection if an intermediate 103 Early Hints response precedes the final HTTP response, or if an ETag header is processed before Content-Disposition under --etag-save. This flaw allows an HTTP(S) server to overwrite an existing local file specified in the Content-Disposition header despite the presence of the -J non-overwrite constraint.

— Launchpad

Affected Software

13 affected componentsFixes available
curl curl
debian/curl<=7.88.1-10+deb12u15, <=7.88.1-10+deb12u5, <=8.14.1-2+deb13u5, <=8.14.1-2+deb13u7, <=8.22.0-1
8.23.0-1
alpine/curl<8.23.0-r0
8.23.0-r0
alpine/curl<8.23.0-r0
8.23.0-r0
debian/curl*
debian/curl*
debian/curl*
ubuntu/curl*
ubuntu/curl*
ubuntu/curl*
ubuntu/curl*
ubuntu/curl<8.20.0-2ubuntu11.1
8.20.0-2ubuntu11.1
ubuntu/curl<8.18.0-1ubuntu2.8
8.18.0-1ubuntu2.8

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/curl to a version that resolves this vulnerability.

    Fixed in 8.23.0-1
  2. Upgrade

    Upgrade alpine/curl to a version that resolves this vulnerability.

    Fixed in 8.23.0-r0
  3. Upgrade

    Upgrade ubuntu/curl to a version that resolves this vulnerability.

    Fixed in 8.20.0-2ubuntu11.1
  4. Upgrade

    Upgrade ubuntu/curl to a version that resolves this vulnerability.

    Fixed in 8.18.0-1ubuntu2.8

Event History

Oct 14, 2026
CVE Published
via OSV·06:00 AM
Data Sourced
via OSV·06:00 AM
DescriptionSeverityAffected Software
Oct 20, 2026
CVE Published
via MITRE·08:23 PM
Data Sourced
via MITRE·08:23 PM
DescriptionWeakness
Data Sourced
via NVD·09:17 PM
DescriptionSeverityWeakness
Oct 23, 2026
Data Sourced
via Microsoft·08:07 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who is exposed to this issue?

Users running curl with --remote-header-name (-J) against an HTTP or HTTPS server are exposed when that server can send a Content-Disposition filename. The bypass is triggered when an intermediate 103 Early Hints response precedes the final response, or when an ETag is processed before Content-Disposition while --etag-save is in use.

2

What must an attacker control to exploit the overwrite?

The attacker needs to control, or be able to influence, the HTTP(S) server response headers, including the Content-Disposition filename. They must also cause the affected response ordering involving 103 Early Hints or ETag handling with --etag-save.

3

Are default curl invocations affected?

The described condition requires --remote-header-name (-J). The provided information does not indicate that curl is affected without this option.

4

What can be done if patching is not immediately possible?

Avoid using --remote-header-name (-J) with untrusted servers, especially where 103 Early Hints responses may be present. Avoid combining -J with --etag-save when the server controls Content-Disposition filenames.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203