vciy

CVE-2007-1862

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.

The recall_headers function in mod_mem_cache in Apache 2.2.4 does not properly copy all levels of header data, which can cause Apache to return HTTP…

CVE-2007-18623 of 4 sources documented this
17

rank 17 = 2 + 13 + 0 + 2 + 0

rank@v1 · backlog

Someone is already using it

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

EPSS 0.06122  ·  without this subject the record ranks 15

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 5.0, from NVD  ·  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 17

How much of the world it touches

NVD CPE configurations

1 product in the CPE ranges  ·  without this subject the record ranks 15

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$87,400over the next 30 days, if this record is yours
Movement+$23,600on 2026-01-21, the last material move, 6 months before this reading
Basisassumeda published average, not your estate

$87,400 = $4.99M incident cost x 0.28625080150224425 exposure x 0.06122 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.06122EPSSNOT IN KEVas of 2026-09-20
Severity5 MEDIUMreceipt
Harmunauthenticated · networkreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementsteadyreceipt
PLATEAU10Minimal movement since 2022-02-04, 1655 days at 0.06, as of 2026-08-17. 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

Check a version against this record

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 authentication · low attack complexityreceipt
ImpactPartial confidentiality lossreceipt
Scored fromCVSS v2.0 · NVD's vectorreceipt
Weakness classNo CWE mapping in held sources.

CISA KEV & Federal Remediation Deadline from the record and CISA

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

Fixed inNo fix version in held sources, as the index stood on 17 Aug 2026.
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, NVD5 MEDIUMreceipt
Exploit probability0.06122 · top 7% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byredhatreceipt
Recorded changes35 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Named in the CPE rangesApache http serverreceipt
Published rangesapache http server 2.2.4receipt

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

The recall_headers function in mod_mem_cache in Apache 2.2.4 does not properly copy all levels of header data, which can cause Apache to return HTTP headers containing previously used data, which could be used by remote attackers to obtain potentially sensitive information. receipt

NVD's analysis a second authority

severity
5 AV:N/AC:L/Au:N/C:P/I:N/A:N
affected versions
apache http server 2.2.4

check it yourself securityfocus.com issues.apache.org people.apache.org secunia.com osvdb.org redhat.com +14 morereceipt

Dated events

2023-03-07EPSS moved 0.07 to 0.002026-06-15EPSS moved 0.14 to 0.05

Movement the material steps

4 Feb 20220.07344
7 Mar 20230.00282 · scoring model v2023.03.01
17 Mar 20250.06328 · scoring model v2025.03.14
29 Mar 20250.10077 · crossed 0.10
30 Mar 20250.06328 · crossed 0.10
15 Jun 20250.11464 · crossed 0.10
10 Dec 20250.09008 · crossed 0.10
27 Dec 20250.16093 · crossed 0.10
28 Dec 20250.09008 · crossed 0.10
21 Jan 20260.10659 · crossed 0.10
15 Jun 20260.05141 · crossed 0.10 · scoring model v2026.06.15
17 Aug 20260.06122
Show all 35 observations
4 Feb 20220.07344
7 Mar 20230.00282
31 Mar 20230.00237
10 Jun 20230.00256
17 Jul 20230.00218
24 Aug 20230.00315
29 Sep 20230.00429
6 Nov 20230.00400
22 Jan 20240.00576
29 Feb 20240.00419
7 Apr 20240.00482
15 May 20240.00749
22 Jun 20240.01060
30 Jul 20240.00771
7 Feb 20250.00628
17 Mar 20250.06328
29 Mar 20250.10077
30 Mar 20250.06328
28 May 20250.08778
15 Jun 20250.11464
30 Jul 20250.16093
1 Oct 20250.11464
10 Oct 20250.11753
27 Oct 20250.16093
28 Oct 20250.11753
10 Dec 20250.09008
27 Dec 20250.16093
28 Dec 20250.09008
21 Jan 20260.10659
13 Jun 20260.13812
15 Jun 20260.05141
19 Jun 20260.05327
11 Jul 20260.05141
17 Jul 20260.05909
17 Aug 20260.06122

35 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.06122Published2007-06-04Index as of2026-08-17

The record had been public for 19 years, 2 months when this index was last written.

Published 2007-06-04 receipt · Index as of 2026-08-17 derived

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2007-1862.

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.