NVD / CVE Program· CNA curl

CVE-2025-15224: libssh key passphrase bypass without agent set

Noroxi assessment

Priority: Monitor (action score 12/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.48% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
Fixed version: curl curl 16d5f2a5660c61cc27bd5f1c7f512391d1c927aa, 8.14.2, 8.16.1.

Low priority for now. Upgrade to curl curl 16d5f2a5660c61cc27bd5f1c7f512391d1c927aa, 8.14.2, 8.16.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

When doing SSH-based transfers using either SCP or SFTP, and asked to do public key authentication, curl would wrongly still ask and authenticate using a locally running SSH agent.

LowCVSS 3.1 · v3.1—No exploit Fix available

Published: Jan 8, 2026
Updated: Oct 14, 2026
EPSS: 0.4% · 41th percentile
CWE: CWE-287

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 12 / 40 · 3.1 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.4%

CISA SSVC decision

Exploitation: proof of concept
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
haxx	curl	cpe:2.3:a:haxx:curl

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

haxx curl7.58.0 and later · before 8.18.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (curl). Independent of NVD's CPE analysis and usually ahead of it.

curl curl
- 8.17.0, 8.16.0, 8.15.0, 8.14.1, 8.14.0, 8.13.0, 8.12.1, 8.12.0, 8.11.1, 8.11.0, 8.10.1, 8.10.0 … (+24)affected
- 7.58.0 and later · before 8.14.2affected · semver
- 8.15.0 and later · before 8.16.1affected · semver
- 8.17.0 and later · before 8.18.0affected · semver
- c92d2e14cfb0db662f958effd2ac86f995cf1b5a and later · before 16d5f2a5660c61cc27bd5f1c7f512391d1c927aaaffected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	curl	from 0	—
Debian:14	curl	before 8.18.0-1	8.18.0-1
openSUSE:Leap 15.6	curl	before 8.14.1-150600.4.34.1	8.14.1-150600.4.34.1
openSUSE:Leap 16.0	curl	before 8.14.1-160000.4.1	8.14.1-160000.4.1
openSUSE:Tumbleweed	curl	before 8.18.0-1.1	8.18.0-1.1
Red Hat:hummingbird:1	curl	before 0:8.19.0-3.hum1	0:8.19.0-3.hum1
Red Hat:hummingbird:1	libcurl	before 0:8.19.0-3.hum1	0:8.19.0-3.hum1
Red Hat:hummingbird:1	libcurl-devel	before 0:8.19.0-3.hum1	0:8.19.0-3.hum1
Red Hat:hummingbird:1	libcurl-minimal	before 0:8.19.0-3.hum1	0:8.19.0-3.hum1
SUSE:Linux Enterprise Micro 5.2	curl	before 8.14.1-150200.4.97.1	8.14.1-150200.4.97.1
SUSE:Linux Enterprise Micro 5.3	curl	before 8.14.1-150400.5.77.1	8.14.1-150400.5.77.1
SUSE:Linux Enterprise Module for Basesystem 15 SP7	curl	before 8.14.1-150700.7.8.1	8.14.1-150700.7.8.1
SUSE:Linux Enterprise Server 16.0	curl	before 8.14.1-160000.4.1	8.14.1-160000.4.1
SUSE:Linux Enterprise Server 16.0	curl-mini	before 8.14.1-160000.4.1	8.14.1-160000.4.1
SUSE:Linux Micro 6.0	curl	before 8.14.1-3.1	8.14.1-3.1
SUSE:Linux Micro 6.1	curl	before 8.14.1-slfo.1.1_4.1	8.14.1-slfo.1.1_4.1

Same product

haxx: all records

Other highest-scoring records for the same primary product.

CVE-2021-22901curl 7.75.0 through 7.76.1 suffers from a use-after-free vulnerability resulting in already freed memory being used when a TLS 1.3 session t
51Plan
CVE-2023-38039When curl retrieves an HTTP response, it stores the incoming headers so that they can be accessed later via the libcurl headers API.
47Plan
CVE-2024-2398HTTP/2 push headers memory-leak
45Plan

Published before and after this one in the same product

← EarlierCVE-2025-14819Jan 8, 2026 · OpenSSL partial chain store policy bypass
21Monitor
← EarlierCVE-2025-15079Jan 8, 2026 · libssh global known_hosts override
21Monitor
Later →CVE-2026-1965Mar 11, 2026 · bad reuse of HTTP Negotiate connection
26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
curl curl	16d5f2a5660c61cc27bd5f1c7f512391d1c927aa	Vendor (CNA)
curl curl	8.14.2	Vendor (CNA)
curl curl	8.16.1	Vendor (CNA)
curl curl	8.18.0	Vendor (CNA)
alpine:curl	0 · Alpine:v3.24	Package registry (OSV)
debian:curl	8.18.0-1 · Debian:14	Package registry (OSV)
opensuse:curl	8.14.1-150600.4.34.1 · openSUSE:Leap 15.6	Package registry (OSV)
red hat:curl	0:8.19.0-3.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:libcurl	0:8.19.0-3.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:libcurl-devel	0:8.19.0-3.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:libcurl-minimal	0:8.19.0-3.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
suse:curl	8.14.1-150200.4.97.1 · SUSE:Linux Enterprise Micro 5.2	Package registry (OSV)
suse:curl-mini	8.14.1-160000.4.1 · SUSE:Linux Enterprise Server 16.0	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Harry Sintonenfinder

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
A user must open a link or visit a page.
Special conditions such as timing or configuration are required.

If successful

Confidentiality: none
Integrity: low · data or configuration can be modified
Availability: none

Attack vector: Network
Attack complexity: High
Privileges required: None
User interaction: Required
Scope: Unchanged
Confidentiality impact: None
Integrity impact: Low
Availability impact: None

Weakness class (CWE)

CWE-287 · Improper Authentication

CVSS vector

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

nvd-secondary

Root cause

Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.

The bug in code

The whole CWE-287 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1app.use("/admin", requireSession, adminRouter);
2

3// Route added later skips the middleware
4app.post("/admin-api/config", updateConfig);

Fixed

1const admin = express.Router();
2admin.use(requireSession, requireRole("admin"));
3

4admin.post("/config", updateConfig);
5app.use("/admin", admin);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Change log

Fix✗ → ✓Sep 28, 2026, 10:11 PM UTC

For records you follow, these changes also arrive as notifications. →

References

curl.se/docs/CVE-2025-15224.html

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records