CVE-2025-58050

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.7%, top 51% 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
Elevated
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.1Exploit: Elevated riskExposed: 0

A fix is available — apply it.

The PCRE2 library is a set of C functions that implement regular expression pattern matching. In version 10.45, a heap-buffer-overflow read vulnerability exists in the PCRE2 regular expression matching engine, specifically within the handling of the (*scs:...) (Scan SubString) verb when combined with (*ACCEPT) in src/pcre2_match.c. This vulnerability may potentially lead to information disclosure if the out-of-bounds data read during the memcmp affects the final match result in a way observable by the attacker. This issue has been resolved in version 10.46.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
72(Attend)
EG Risk 72/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
Severity91% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
55%
KEV
Not listed

Published

August 27, 2025

Last Modified

September 9, 2025

Advisory Details (3)

Auto-updated Aug 1, 2026
Patch available. Sources: github_commit, github_release, github.
github Patch Available

[BIGSLEEP-438254142] PCRE2: heap-buffer-overflow read in match_ref due to missing boundary restoration in SCS · Advisory · PCRE2Project/pcre2 · GitHub

https://github.com/PCRE2Project/pcre2/security/advisories/GHSA-c2gv-xgf5-5cc2
github_release Patch Available

PCRE2-10.46

Patch available: PCRE2Project/pcre2 pcre2-10.46

https://github.com/PCRE2Project/pcre2/releases/tag/pcre2-10.46
github_commit

commit a141712e5967 (PCRE2Project/pcre2)

Fix landed in PCRE2Project/pcre2 commit a141712e5967 — awaiting tagged release

https://github.com/PCRE2Project/pcre2/commit/a141712e5967d448c7ce13090ab530c8e3d82254

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupcre2-utils (10.45-1ubuntu0.1) @ plucky2026-05-29ubuntu

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

(6 across 6 ecosystems)
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
pcre2—10.46-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
pcre2—10.46-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
pcre2—10.46-r0—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
pcre210.45-110.46-1~deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
pcre210.45-1, 10.46-1~deb13u110.46-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
pcre20.1.0 ... 0.7.0 (10 versions)——

Weakness Classification(3)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 32× 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 155 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-58050?
CVE-2025-58050 is a critical vulnerability published on August 27, 2025. The PCRE2 library is a set of C functions that implement regular expression pattern matching. In version 10.45, a heap-buffer-overflow read vulnerability exists in the PCRE2 regular expression matching engine, specifically within the handling of the (scs:...) (Scan SubString) verb when combined…
When was CVE-2025-58050 disclosed?
CVE-2025-58050 was first published in the National Vulnerability Database on August 27, 2025, with the most recent update on September 9, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-58050 actively exploited?
CVE-2025-58050 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 45.0% of all scored CVEs.
What is the CVSS score of CVE-2025-58050?
CVE-2025-58050 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2025-58050?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-58050, 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-58050

Explore →

Is Your Infrastructure Affected by CVE-2025-58050?

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

Start Free Scan →Browse All CVEs