CVE-2025-69873

HIGHPre-NVD 7.52.9▼
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.9 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 97% 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: epss, nvd
Trending — 4 sources updated this weekElevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 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
7.5
EG Score
2.9(medium)
EPSS
39.0%
KEV
Not listed

Published

February 11, 2026

Last Modified

July 16, 2026

Advisory Details (9)

Auto-updated Jun 30, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, redhat.
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:15091
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:14774
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:13512
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:10093
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

Vendor Advisories for CVE-2025-69873(20)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(19)

Vendor / EcosystemFixed in / PatchReleasedSource
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
redhatquay/quay-rhel9:17750694912026-04-02redhat
redhatopenshift4/ose-monitoring-plugin-rhel9:17744526492026-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

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
ajv—6.14.0—

Weakness Classification(2)

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

Additional Vendor Advisories

(6)

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 15× in last 7d / 54× 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 113 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-69873?
CVE-2025-69873 is a high 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 July 16, 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 39.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-69873?
CVE-2025-69873 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 2.9.
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.

Start Free Scan →Browse All CVEs