CVE-2010-4051

NONECVSS 0.0Elevated
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 40%CVSS: —Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The regcomp implementation in the GNU C Library (aka glibc or libc6) through 2.11.3, and 2.12.x through 2.12.2, allows context-dependent attackers to cause a denial of service (application crash) via a regular expression containing adjacent bounded repetitions that bypass the intended RE_DUP_MAX limitation, as demonstrated by a {10,}{10,}{10,}{10,}{10,} sequence in the proftpd.gnu.c exploit for ProFTPD, related to a "RE_DUP_MAX overflow."

CVSS v3
—
EG Score
0.0(none)
EPSS
98.5%
KEV
Not listed

Published

January 13, 2011

Last Modified

April 29, 2026

References (24)

Data Freshness Timeline

(refreshed 4× 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.

  1. 2026-07-05 21:59 UTCOSV refresh
  2. 2026-07-05 02:26 UTCEPSS rescore
  3. 2026-07-02 14:01 UTCEPSS rescore
  4. 2026-07-01 15:02 UTCEPSS rescore
  5. 2026-06-28 14:03 UTCEPSS rescore
  6. 2026-06-28 04:52 UTCEPSS rescore
  7. 2026-06-28 04:52 UTCEPSS rescore
  8. 2026-06-25 13:46 UTCEPSS rescore
  9. 2026-06-24 14:02 UTCEPSS rescore
  10. 2026-06-24 14:02 UTCEPSS rescore
  11. 2026-06-23 21:30 UTCEPSS rescore
  12. 2026-06-23 21:29 UTCEPSS rescore
  13. 2026-06-22 14:22 UTCEPSS rescore
  14. 2026-06-22 14:22 UTCEPSS rescore
  15. 2026-06-21 01:56 UTCEPSS rescore
  16. 2026-06-21 01:56 UTCEPSS rescore
  17. 2026-06-18 17:49 UTCEPSS rescore
  18. 2026-06-18 17:49 UTCEPSS rescore
  19. 2026-06-17 17:49 UTCEPSS rescore
  20. 2026-06-17 17:49 UTCEPSS rescore
  21. 2026-06-17 09:14 UTCOSV refresh
  22. 2026-06-16 17:49 UTCEPSS rescore
  23. 2026-06-15 17:44 UTCEPSS rescore
  24. 2026-06-13 22:57 UTCEPSS rescore
  25. 2026-06-13 22:57 UTCEPSS rescore
Show 43 more
  1. 2026-06-13 22:57 UTCEPSS rescore
  2. 2026-06-12 23:08 UTCEPSS rescore
  3. 2026-06-12 23:08 UTCEPSS rescore
  4. 2026-06-11 13:56 UTCEPSS rescore
  5. 2026-06-10 22:14 UTCEPSS rescore
  6. 2026-06-10 13:17 UTCEPSS rescore
  7. 2026-06-08 14:13 UTCEPSS rescore
  8. 2026-06-07 15:22 UTCEPSS rescore
  9. 2026-06-07 15:22 UTCEPSS rescore
  10. 2026-06-06 13:44 UTCEPSS rescore
  11. 2026-06-06 13:44 UTCEPSS rescore
  12. 2026-06-05 22:44 UTCEPSS rescore
  13. 2026-06-05 22:44 UTCEPSS rescore
  14. 2026-06-05 06:07 UTCEPSS rescore
  15. 2026-06-05 06:07 UTCEPSS rescore
  16. 2026-06-04 13:09 UTCEPSS rescore
  17. 2026-06-04 13:09 UTCEPSS rescore
  18. 2026-06-02 20:10 UTCEPSS rescore
  19. 2026-06-02 20:10 UTCEPSS rescore
  20. 2026-05-31 22:28 UTCEPSS rescore
  21. 2026-05-31 22:28 UTCEPSS rescore
  22. 2026-05-31 00:14 UTCEPSS rescore
  23. 2026-05-31 00:13 UTCEPSS rescore
  24. 2026-05-29 13:40 UTCEPSS rescore
  25. 2026-05-29 09:14 UTCEG score recompute
  26. 2026-05-29 09:13 UTCGHSA enrichment
  27. 2026-05-28 13:42 UTCEPSS rescore
  28. 2026-05-28 13:42 UTCEPSS rescore
  29. 2026-05-27 13:38 UTCEPSS rescore
  30. 2026-05-27 13:38 UTCEPSS rescore
  31. 2026-05-26 13:41 UTCEPSS rescore
  32. 2026-05-26 13:41 UTCEPSS rescore
  33. 2026-05-26 07:16 UTCEPSS rescore
  34. 2026-05-26 07:16 UTCEPSS rescore
  35. 2026-05-24 16:43 UTCEPSS rescore
  36. 2026-05-21 22:39 UTCEPSS rescore
  37. 2026-05-20 22:37 UTCEPSS rescore
  38. 2026-05-20 22:37 UTCEPSS rescore
  39. 2026-05-20 22:37 UTCEPSS rescore
  40. 2026-05-20 11:21 UTCEPSS rescore
  41. 2026-05-20 11:21 UTCEPSS rescore
  42. 2026-05-18 21:29 UTCEPSS rescore
  43. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-15935
    First seen Jan 7, 2011

    GNU libc/regcomp(3) - Multiple Vulnerabilities

    Open source ↗

Frequently asked(4)

What is CVE-2010-4051?
CVE-2010-4051 is a none vulnerability published on January 13, 2011. The regcomp implementation in the GNU C Library (aka glibc or libc6) through 2.11.3, and 2.12.x through 2.12.2, allows context-dependent attackers to cause a denial of service (application crash) via a regular expression containing adjacent bounded repetitions that bypass the intended REDUPMAX…
When was CVE-2010-4051 disclosed?
CVE-2010-4051 was first published in the National Vulnerability Database on January 13, 2011, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2010-4051 actively exploited?
CVE-2010-4051 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2010-4051?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2010-4051, 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

Explore the affected products and dependency analysis for CVE-2010-4051

Explore →

Is Your Infrastructure Affected by CVE-2010-4051?

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

Start Free Scan →Browse All CVEs