CVE-2026-42002

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 82% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

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

Concurrency and locking defects in GSS-TSIG

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
34(Track)
EG Risk 34/100SSVC: Track

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
Severity75% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
18%
KEV
Not listed

Published

May 21, 2026

Last Modified

July 23, 2026

References (1)

Vendor Advisories for CVE-2026-42002(1)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
pdns4.4.1-1 ... 5.1.3-1 (53 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
pdns4.7.3-2 ... 5.1.3-1 (40 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
pdns4.9.14-0+deb13u1, 4.9.7-14.9.15-0+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
pdns4.9.7-1 ... 5.0.4-1 (7 versions)5.0.5-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 76× 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 188 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-42002?
CVE-2026-42002 is a high vulnerability published on May 21, 2026. Concurrency and locking defects in GSS-TSIG
When was CVE-2026-42002 disclosed?
CVE-2026-42002 was first published in the National Vulnerability Database on May 21, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42002 actively exploited?
CVE-2026-42002 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 82.2% of all scored CVEs.
What is the CVSS score of CVE-2026-42002?
CVE-2026-42002 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-42002?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42002, 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-2026-42002

Explore →

Is Your Infrastructure Affected by CVE-2026-42002?

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

Start Free Scan →Browse All CVEs