vciy

CVE-2024-38476

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.

Apache HTTP Server may use exploitable/malicious backend application output to run local handlers via internal redirect

CVE-2024-384764 of 4 sources documented this
52

rank 52 = 21 + 25 + 2 + 4 + 0

rank@v1 · this cycle

Someone is already using it

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

EPSS 0.41611  ·  without this subject the record ranks 31

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 9.8, from NVD  ·  without this subject the record ranks 27

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2025-11-18  ·  without this subject the record ranks 50

How much of the world it touches

NVD CPE configurations

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

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$2.08Mover the next 30 days, if this record is yours
Movement-$510,000on 2025-11-21, the last material move, 6 months before this reading
Basisassumeda published average, not your estate

$2.08M = $4.99M incident cost x 1 exposure x 0.41611 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.41611EPSSNOT IN KEVas of 2026-09-20
Severity9.8 CRITICALreceipt
Harmtotal loss · unauthenticatedreceipt
Exploitationpublic proof-of-conceptreceipt
Defenseunaffected versions publishedreceipt
Movementthreshold crossedreceipt
RISING10Risen from 0.00043 to 0.41611 across 84 observations. arc-rules@v1

Foresight · where to check next

LangflowSudo38476

This record is one instance of CWE-829, inclusion of functionality from untrusted control sphere. The index holds 333 prior instances of this class, 2 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signalspoke length is how much of the record matches, not how bad it is

Running Apache HTTP Server? 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 · no privileges required · no user interaction · low attack complexityreceipt
ImpactComplete confidentiality, integrity and availability lossreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classCWE-829 Inclusion of Functionality from Untrusted Control Spherereceipt
Published consequencesCWE-829: Confidentiality, Integrity, Availability: Execute Unauthorized Code or Commands[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

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

First unaffected version, by branchhttp server 2.4.60receipt
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: Proof-of-concept published · 1 public repository, 2026-01-21.

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

Authority who says so

CVSS, NVD9.8 CRITICALreceipt
Exploit probability0.41611 · top 1% of all CVEsreceipt
Blast breadth2 products across 2 vendorsderived
Assigned byapachereceipt
Recorded changes87 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productApache Software Foundation Apache HTTP Serverreceipt
Published rangesapache http server >= 2.4.0 < 2.4.60; netapp clustered data ontap 9.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

Vulnerability in core of Apache HTTP Server 2.4.59 and earlier are vulnerably to information disclosure, SSRF or local script execution via backend applications whose response headers are malicious or exploitable. Users are recommended to upgrade to version 2.4.60, which fixes this issue. receipt

NVD's analysis a second authority

severity
9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
weakness
CWE-829
affected versions
apache http server >= 2.4.0 < 2.4.60; netapp clustered data ontap 9.0
also scored by
9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

check it yourself httpd.apache.org security.netapp.com receipt

Dated events

2025-03-19EPSS moved 0.05 to 0.202026-06-15EPSS moved 0.03 to 0.42

Movement the material steps

2 Jul 20240.00043
17 Mar 20250.04892 · scoring model v2025.03.14
19 Mar 20250.20265 · crossed 0.10
20 Mar 20250.04892 · crossed 0.10
27 Mar 20250.24843 · crossed 0.10
28 Mar 20250.06348 · crossed 0.10
29 Mar 20250.24843 · crossed 0.10
30 Mar 20250.06348 · crossed 0.10
18 Nov 20250.13773 · crossed 0.10
21 Nov 20250.03545 · crossed 0.10
15 Jun 20260.41611 · crossed 0.10 · scoring model v2026.06.15

This score more than doubled inside 72 hours. Both observations are in the full history below.

Show all 84 observations
2 Jul 20240.00043
22 Aug 20240.01295
13 Sep 20240.01825
17 Mar 20250.04892
19 Mar 20250.20265
20 Mar 20250.04892
27 Mar 20250.24843
28 Mar 20250.06348
29 Mar 20250.24843
30 Mar 20250.06348
15 Apr 20250.00987
17 Apr 20250.01322
27 Apr 20250.01393
1 May 20250.00691
4 May 20250.01393
15 May 20250.01155
17 May 20250.01393
1 Jun 20250.00691
4 Jun 20250.01393
15 Jun 20250.01198
25 Jun 20250.01393
1 Jul 20250.00691
4 Jul 20250.01393
5 Jul 20250.01155
7 Jul 20250.01393
9 Jul 20250.01198
12 Jul 20250.01393
30 Jul 20250.01085
1 Aug 20250.00639
4 Aug 20250.01085
9 Aug 20250.01917
10 Aug 20250.02002
15 Aug 20250.01866
16 Aug 20250.01917
19 Aug 20250.01651
20 Aug 20250.02057
24 Aug 20250.01917
1 Sep 20250.01178
4 Sep 20250.02002
13 Sep 20250.01866
16 Sep 20250.01771
23 Sep 20250.01651
29 Sep 20250.02057
1 Oct 20250.0144
4 Oct 20250.0289
6 Oct 20250.02815
7 Oct 20250.0289
19 Oct 20250.02697
20 Oct 20250.02815
21 Oct 20250.0289
27 Oct 20250.02057
28 Oct 20250.0289
30 Oct 20250.02697
1 Nov 20250.01342
3 Nov 20250.01306
4 Nov 20250.02981
8 Nov 20250.03061
18 Nov 20250.13773
21 Nov 20250.03545
24 Nov 20250.03452
1 Dec 20250.01813
4 Dec 20250.03545
14 Dec 20250.03452
27 Dec 20250.02167
28 Dec 20250.03452
1 Jan 20260.01764
4 Jan 20260.03452
13 Jan 20260.03545
15 Jan 20260.03452
21 Jan 20260.03545
1 Feb 20260.01813
3 Feb 20260.01764
4 Feb 20260.03452
1 Mar 20260.01764
4 Mar 20260.03452
24 Mar 20260.03545
6 Apr 20260.03452
14 Apr 20260.04554
21 Apr 20260.04673
27 Apr 20260.04554
26 May 20260.04673
8 Jun 20260.04554
12 Jun 20260.03019
15 Jun 20260.41611

84 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.41611Published2024-07-01Public PoC2026-01-21Index as of2026-06-15

Exploit probability more than doubled between 2025-03-17 and 2025-03-19 (0.04892 → 0.20265) and the record had been public for 1 year, 11 months when this index was last written.

Published 2024-07-01 receipt · Public PoC 2026-01-21 receipt · Index as of 2026-06-15 derived

The pattern, elsewhere

This record is one instance of CWE-829, inclusion of functionality from untrusted control sphere. The index holds 333 prior instances of this class, 2 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2026-0770 · Langflowmatches 8 of 9KEV listed · 2026receipt
CVE-2025-32463 · Sudomatches 6 of 9KEV listed · 2025receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

333 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Fixed with these, by one advisory

vulnerabilities_24

Of the 7 records in this advisory, this is the only one with public proof-of-concept code, and it holds 1 references to it.

Listed because one advisory covers them, not because they are the same defect. Each record's own state is on its own page.

Grouping: held values

Browse the index from here

These are index-wide views, not findings about CVE-2024-38476.

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.