vciy

CVE-2026-1527

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

undici is vulnerable to CRLF Injection via upgrade option

CVE-2026-15274 of 4 sources documented this
16

rank 16 = 0 + 12 + 0 + 4 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.00276  ·  without this subject the record ranks 16

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 4.6, from the CNA  ·  without this subject the record ranks 4

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 16

How much of the world it touches

NVD CPE configurations

2 products in the CPE ranges  ·  without this subject the record ranks 12

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 16

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$5,900over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$5,900 = $4.99M incident cost x 0.42806422275080447 exposure x 0.00276 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.00276EPSSNOT IN KEVas of 2026-09-20
Severity4.6 MEDIUMreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defensefix version namedreceipt
Movementrisenreceipt
PLATEAU10Minimal movement since 2026-03-13, 168 days at 0.00, as of 2026-08-28. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Running undici? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · low privileges required · user interaction required · low attack complexityreceipt
ImpactPartial confidentiality and integrity lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-93 Improper Neutralization of CRLF Sequences ('CRLF Injection')receipt
Published consequencesCWE-93: Integrity: Modify Application Data[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed in6.24.0: 7.24.0receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, the CNA4.6 MEDIUMreceipt
Exploit probability0.00276 · top 80% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byopenjsreceipt
Recorded changes8 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productundicireceipt
Published rangesnodejs undici < 6.24.0; nodejs undici >= 7.0.0 < 7.24.0receipt
Fixed in6.24.0: 7.24.0receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

ImpactWhen an application passes user-controlled input to the upgrade option of client.request(), an attacker can inject CRLF sequences (\r\n) to: * Inject arbitrary HTTP headers * Terminate the HTTP request prematurely and smuggle raw data to non-HTTP services (Redis, Memcached, Elasticsearch) The vulnerability exists because undici writes the upgrade value directly to the socket without validating for invalid header characters: // lib/dispatcher/client-h1.js:1121 if (upgrade) { header += `connection: upgrade\r\nupgrade: ${upgrade}\r\n` } receipt

NVD's analysis a second authority

weakness
CWE-93
affected versions
nodejs undici < 6.24.0; nodejs undici >= 7.0.0 < 7.24.0
also scored by
4.6 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N

check it yourself github.com hackerone.com cna.openjsf.org receipt

Movement the material steps

13 Mar 20260.00029
15 Jun 20260.00256 · scoring model v2026.06.15
28 Aug 20260.00276
Show all 8 observations
13 Mar 20260.00029
17 Mar 20260.00022
18 Mar 20260.00023
21 Mar 20269e-05
13 Apr 20260.00011
19 May 20260.00012
15 Jun 20260.00256
28 Aug 20260.00276

8 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.00276Published2026-03-12Index as of2026-08-28

The record had been public for 5 months when this index was last written.

Published 2026-03-12 receipt · Index as of 2026-08-28 derived

Siblings and hubs

Records related to this one

Its defect family

undici

Of the 3 records in this family, this is the only one holding a stated fix version: 6.24.0: 7.24.0.

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Family membership: held values

This record is one of a group, and the group's page describes all of them. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.

Browse the index from here

These are index-wide views, not findings about CVE-2026-1527.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.