CVE-2025-69873

LOWPre-NVD 2.92.9
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.9 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 59% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:mitre, epss
Trending — 4 sources updated this weekElevated
2.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 2.9Exploit: Elevated riskExposed: 0

A fix is available — apply it.

ajv (Another JSON Schema Validator) before 8.18.0 is vulnerable to Regular Expression Denial of Service (ReDoS) when the $data option is enabled. The pattern keyword accepts runtime data via JSON Pointer syntax ($data reference), which is passed directly to the JavaScript RegExp() constructor without validation. An attacker can inject a malicious regex pattern (e.g., "^(a|a)*$") combined with crafted input to cause catastrophic backtracking. A 31-character payload causes approximately 44 seconds of CPU blocking, with each additional character doubling execution time. This enables complete denial of service with a single HTTP request against any API using ajv with $data: true for dynamic schema validation. This issue is also fixed in version 6.14.0.

CVSS v3
2.9
EG Score
2.9(medium)
EG Risk
44(Attend)
EG Risk 44/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity29% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
42%
KEV
Not listed

Published

February 11, 2026

Last Modified

September 14, 2026

Advisory Details (9)

Auto-updated Jun 30, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, redhat.
github_pr

[GHSA-2g4f-4pwh-qvx6] ajv has ReDoS when using `$data` option

Fix merged in github/advisory-database PR #6991 on 2026-02-20 — awaiting tagged release

https://github.com/github/advisory-database/pull/6991
github_pr

add regExp option to address $data exploit via a regular expression (CVE-2025-69873)

Fix merged in ajv-validator/ajv PR #2590 on 2026-02-20 — awaiting tagged release

https://github.com/ajv-validator/ajv/pull/2590
github_pr

fix(security): backport CVE-2025-69873 - wrap $data pattern in try/catch

Upstream fix in progress (PR #2588 · ajv-validator/ajv, state=closed)

https://github.com/ajv-validator/ajv/pull/2588
github Patch Available

ajv has ReDoS when using `$data` option · CVE-2025-69873 · GitHub Advisory Database · GitHub

https://github.com/advisories/GHSA-2g4f-4pwh-qvx6
generic🟡 PoC Available

ethan-cve-disclosures/CVE-2025-69873-ajv-ReDoS.md at main · EthanKim88/ethan-cve-disclosures · GitHub

https://github.com/EthanKim88/ethan-cve-disclosures/blob/main/CVE-2025-69873-ajv-ReDoS.md

Patch Availability(28)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatodf4/rook-ceph-rhel9-operator:17836853752026-07-20redhat
redhatodf4/rook-ceph-rhel9-operator:17836775332026-07-20redhat
redhatrhem/flightctl-ui-rhel10:17841945742026-07-16redhat
redhatodf4/rook-ceph-rhel9-operator:17836692192026-07-16redhat
redhatrhem/flightctl-ui-rhel9:17841277362026-07-15redhat
redhatrhem/flightctl-ui-rhel9:17835024382026-07-08redhat
redhateap7-wildfly-0:7.3.18-3.GA_redhat_00001.1.el7eap2026-06-30redhat
redhatsatellite/iop-advisor-frontend-rhel9:17811816732026-06-16redhat
redhatsatellite/iop-remediations-rhel9:17812470252026-06-16redhat
redhatrhoai/odh-mod-arch-model-registry-rhel9:17786669872026-05-20redhat
redhatopenshift4/ose-monitoring-plugin-rhel8:17779948442026-05-13redhat
redhatnetwork-observability/network-observability-console-plugin-compat-rhel9:17785089562026-05-13redhat
redhatopenshift4/ose-monitoring-plugin-rhel8:17780366412026-05-12redhat
redhatautomation-gateway-0:2.5.20260422-2.el9ap2026-05-04redhat
redhatopenshift4/ose-monitoring-plugin-rhel9:17766758722026-04-29redhat
redhatrhdh/rhdh-hub-rhel9:17767842862026-04-22redhat
redhatquay/quay-rhel8:17755121632026-04-09redhat
redhatrhdh/rhdh-hub-rhel9:17751406472026-04-07redhat
redhatquay/quay-rhel9:17751692262026-04-03redhat
redhatquay/quay-rhel8:17751692192026-04-03redhat
redhatopenshift4/ose-monitoring-plugin-rhel9:17744526492026-04-02redhat
redhatquay/quay-rhel9:17750694912026-04-02redhat
redhatopenshift4/ose-monitoring-plugin-rhel9:17744749082026-04-01redhat
redhatansible-automation-platform-26/gateway-rhel9:17742438622026-04-01redhat
redhatautomation-platform-ui-0:2.6.7-1.el9ap2026-03-31redhat
redhatdevspaces/dashboard-rhel9:17744765262026-03-30redhat
redhatrhoai/odh-dashboard-rhel8:17742821362026-03-25redhat
redhatquay/quay-rhel8:17739363232026-03-19redhat

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
node-ajv6.12.6-2 ... 8.8.2~ds+~2.1.1-1 (18 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
node-ajv6.12.6-3 ... 8.8.2~ds+~2.1.1-1 (21 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-ajv8.12.0~ds+~2.1.1-5 ... 8.20.0~ds+~cs7.1.5-1 (14 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-ajv8.12.0~ds+~2.1.1-5, 8.17.1~ds+~3.0.1+~3.1.0-1, 8.17.1~ds+~3.0.1+~3.1.0-2, 8.17.1~ds+~3.0.1+~3.1.0-3, 8.17.1~ds+~3.0.1+~3.1.0-48.18.0~ds+~cs6.1.1-1
npm(1)
PackageVulnerable rangeFixed inDependents
ajv6.14.0

Weakness Classification(2)

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

Additional Vendor Advisories

(9)

Data Freshness Timeline

(refreshed 10× in last 7d / 64× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 286 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-69873?
CVE-2025-69873 is a low vulnerability published on February 11, 2026. ajv (Another JSON Schema Validator) before 8.18.0 is vulnerable to Regular Expression Denial of Service (ReDoS) when the $data option is enabled. The pattern keyword accepts runtime data via JSON Pointer syntax ($data reference), which is passed directly to the JavaScript RegExp() constructor…
When was CVE-2025-69873 disclosed?
CVE-2025-69873 was first published in the National Vulnerability Database on February 11, 2026, with the most recent update on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-69873 actively exploited?
CVE-2025-69873 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 58.2% of all scored CVEs.
What is the CVSS score of CVE-2025-69873?
CVE-2025-69873 has a CVSS v4.0 base score of 2.9 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2025-69873?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-69873, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-69873?

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