CVE-2025-1861

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.9% (58th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2025-15117 (ENISA EUVD)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In PHP from 8.1.* before 8.1.32, from 8.2.* before 8.2.28, from 8.3.* before 8.3.19, from 8.4.* before 8.4.5, when parsing HTTP redirect in the response to an HTTP request, there is currently limit on the location value size caused by limited size of the location buffer to 1024. However as per RFC9110, the limit is recommended to be 8000. This may lead to incorrect URL truncation and redirecting to a wrong location.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.9% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.9%
EPSS %ILE
58th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 30, 2025

Last Modified

November 3, 2025

Advisory Details (3)

Auto-updated Oct 9, 2026
Patch available. Sources: github.
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4088-1] php7.4 security update

https://lists.debian.org/debian-lts-announce/2025/03/msg00014.html
GitHub advisoryMentions a patch (unverified)

Stream HTTP wrapper truncate redirect location to 1024 bytes · Advisory · php/php-src · GitHub

https://github.com/php/php-src/security/advisories/GHSA-52jp-hrpf-2jff

Patch Availability(9)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuphp7.0-zip (7.0.33-0ubuntu0.16.04.16+esm15) @ xenial2026-11-01ubuntu
ubuntuphp8.1-zip (8.1.2-1ubuntu2.21) @ jammy2026-11-01ubuntu
redhatphp:7.4-8100020260119075152.f79986652026-02-10redhat
redhatphp:8.2-8100020250903052702.f79986652025-09-11redhat
redhatphp-0:8.3.19-1.el10_02025-05-13redhat
redhatphp:8.3-9060020250409105946.92025-05-13redhat
redhatphp-0:8.0.30-3.el9_62025-05-13redhat
redhatphp:8.2-9060020250428130539.92025-05-13redhat
redhatphp:8.1-9050020250423093228.92025-04-28redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
php7.47.4.21-1+deb11u1 ... 7.4.33-1+deb11u7 (11 versions)
  • every version up to 7.4.33-1+deb11u8: fixed in 7.4.33-1+deb11u8
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
php8.28.2.10-1 ... 8.2.7-1~deb12u1 (23 versions)
  • every version up to 8.2.28-1~deb12u1: fixed in 8.2.28-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
php8.4—
  • every version up to 8.4.5-1: fixed in 8.4.5-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
php8.4—
  • every version up to 8.4.5-1: fixed in 8.4.5-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 21× in last 7d / 75× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 229 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 131 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 20:23 UTCEG score recompute
  2. 2026-11-01 20:23 UTCVendor advisory
  3. 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  4. 2026-10-31 22:08 UTCEG score recompute
  5. 2026-10-31 22:08 UTCVendor advisory
  6. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  7. 2026-10-30 23:48 UTCEG score recompute
  8. 2026-10-30 23:48 UTCVendor advisory
  9. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  10. 2026-10-30 01:31 UTCEG score recompute
  11. 2026-10-30 01:31 UTCVendor advisory
  12. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  13. 2026-10-29 03:16 UTCEG score recompute
  14. 2026-10-29 03:16 UTCVendor advisory
  15. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  16. 2026-10-28 05:00 UTCEG score recompute
  17. 2026-10-28 05:00 UTCVendor advisory
  18. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  19. 2026-10-27 06:44 UTCEG score recompute
  20. 2026-10-27 06:44 UTCVendor advisory
  21. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  22. 2026-10-26 04:56 UTCVendor advisory
  23. 2026-10-25 16:44 UTCEG score recompute
  24. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  25. 2026-10-25 06:41 UTCEG score recompute
Show 73 more
  1. 2026-10-25 06:41 UTCVendor advisory
  2. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  3. 2026-10-24 08:24 UTCEG score recompute
  4. 2026-10-24 08:24 UTCVendor advisory
  5. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  6. 2026-10-23 10:08 UTCEG score recompute
  7. 2026-10-23 10:08 UTCVendor advisory
  8. 2026-10-22 16:32 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  9. 2026-10-22 11:46 UTCEG score recompute
  10. 2026-10-22 11:46 UTCVendor advisory
  11. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  12. 2026-10-21 13:28 UTCEG score recompute
  13. 2026-10-21 13:28 UTCVendor advisory
  14. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  15. 2026-10-20 15:11 UTCEG score recompute
  16. 2026-10-20 15:11 UTCVendor advisory
  17. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  18. 2026-10-19 15:17 UTCVendor advisory
  19. 2026-10-18 16:58 UTCEG score recompute
  20. 2026-10-18 16:58 UTCVendor advisory
  21. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  22. 2026-10-18 05:47 UTCEG score recompute
  23. 2026-10-17 18:40 UTCEG score recompute
  24. 2026-10-17 18:40 UTCVendor advisory
  25. 2026-10-17 16:32 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  26. 2026-10-16 20:22 UTCEG score recompute
  27. 2026-10-16 20:22 UTCVendor advisory
  28. 2026-10-16 16:37 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  29. 2026-10-15 17:49 UTCEG score recompute
  30. 2026-10-15 17:49 UTCVendor advisory
  31. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  32. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  33. 2026-10-14 11:42 UTCEG score recompute
  34. 2026-10-14 11:42 UTCVendor advisory
  35. 2026-10-13 16:31 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  36. 2026-10-13 10:44 UTCVendor advisory
  37. 2026-10-12 17:21 UTCEG score recompute
  38. 2026-10-12 16:32 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  39. 2026-10-12 12:10 UTCVendor advisory
  40. 2026-10-11 20:52 UTCEG score recompute
  41. 2026-10-11 19:02 UTCEG score recompute
  42. 2026-10-11 15:43 UTCEG score recompute
  43. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  44. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  45. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  46. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  47. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  48. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  49. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  50. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  51. 2026-10-02 18:55 UTCOSV refresh
  52. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  53. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  54. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  55. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  56. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  57. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  58. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  59. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  60. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  61. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  62. 2026-09-16 05:13 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  63. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  64. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  65. 2026-09-13 16:24 UTCOSV refresh
  66. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  67. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  68. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  69. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  70. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  71. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  72. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  73. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.8% · 54th percentile

Frequently asked(5)

What is CVE-2025-1861?
CVE-2025-1861 is a critical-severity vulnerability; its CVE record was published on March 30, 2025. In PHP from 8.1.* before 8.1.32, from 8.2.* before 8.2.28, from 8.3.* before 8.3.19, from 8.4.* before 8.4.5, when parsing HTTP redirect in the response to an HTTP request, there is currently limit on the location value size caused by limited size of the location buffer to 1024. However as per…
When was CVE-2025-1861 made public?
CVE-2025-1861 was made public on March 23, 2025: that is the date its CVE record's CNA, PHP Group, gives for when the vulnerability was made public. The CVE record itself was published on March 30, 2025. EchelonGraph's copy of the record carries a last-modified date of November 3, 2025; the record at its source may have been updated since.
Is CVE-2025-1861 actively exploited?
CVE-2025-1861 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (58th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-1861?
CVE-2025-1861 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2025-1861?
A fix for CVE-2025-1861 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-1861 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-1861

Explore →

Is Your Infrastructure Affected by CVE-2025-1861?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.