CVE-2023-50387

CRITICALNVD 7.59.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because EPSS predicted >99.9% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekElevated

Also known asEUVD-2023-55182 (ENISA EUVD) · GHSA-8459-gg55-8qjj (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS >99.9%
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: >99.9%CVSS: 7.5Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the "KeyTrap" issue. One of the concerns is that, when there is a zone with many DNSKEY and RRSIG records, the protocol specification implies that an algorithm must evaluate all combinations of DNSKEY and RRSIG records.

CVSS v3
7.5
EG Score
9.0CRITICALhigh confidence
EG Risk
89
EG Risk 89/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation>99.9% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
>99.9%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 7.5 HIGH): a likelihood of exploitation, not impact.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
>99.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

February 14, 2024

Last Modified

November 4, 2025

Advisory Details (10)

Auto-updated Oct 12, 2026
Patch available. Sources: redhat.
Web page

[SECURITY] Fedora 38 Update: unbound-1.19.1-1.fc38 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6FV5O347JTX7P5OZA6NGO4MKTXRXMKOZ/
Web pageMentions a patch (unverified)

[SECURITY] [DLA 3816-1] bind9 security update

https://lists.debian.org/debian-lts-announce/2024/05/msg00011.html
Web pageMentions a patch (unverified)

[SECURITY] [DLA 3736-1] unbound security update

https://lists.debian.org/debian-lts-announce/2024/02/msg00006.html
Web page

v5.7.1 · Knot projects / Knot Resolver · GitLab

https://gitlab.nic.cz/knot/knot-resolver/-/releases/v5.7.1
Web page

PowerDNS Security Advisory 2024-01: crafted DNSSEC records in a zone can lead to a denial of service in Recursor - PowerDNS Recursor documentation

https://docs.powerdns.com/recursor/security-advisories/powerdns-advisory-2024-01.html
Web page

Making sure you're not a bot!

https://bugzilla.suse.com/show_bug.cgi?id=1219823
Red HatMentions a patch (unverified)

CVE-2023-50387 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2023-50387
Web page

oss-security - Re: Unbound: disclosure of CVE-2023-50387 and CVE-2023-50868 DNSSEC validation vulnerabilities

http://www.openwall.com/lists/oss-security/2024/02/16/3
Web page

oss-security - Re: Unbound: disclosure of CVE-2023-50387 and CVE-2023-50868 DNSSEC validation vulnerabilities

http://www.openwall.com/lists/oss-security/2024/02/16/2

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatbind-dyndb-ldap-0:2.3-8.el6_10.12025-01-06redhat
redhatunbound-0:1.6.6-5.el7_9.12024-12-12redhat
redhatdnsmasq-0:2.79-11.el8_2.32024-06-13redhat
redhatdnsmasq-0:2.79-15.el8_4.22024-06-13redhat
redhatdhcp-12:4.2.5-83.el7_9.22024-06-10redhat
redhatbind-32:9.11.36-14.el8_102024-05-22redhat
redhatdhcp-12:4.3.6-40.el8_2.32024-05-16redhat
redhatdhcp-12:4.3.6-44.el8_4.32024-05-13redhat
redhatdhcp-12:4.3.6-49.el8_8.12024-05-07redhat
redhatdhcp-12:4.3.6-47.el8_6.22024-05-07redhat
redhatunbound-0:1.7.3-12.el8_2.12024-05-06redhat
redhatbind-dyndb-ldap-0:11.9-9.el9_42024-04-30redhat
redhatunbound-0:1.7.3-15.el8_4.12024-04-30redhat
redhatunbound-0:1.13.1-13.el9_0.42024-04-15redhat
redhatbind-dyndb-ldap-0:11.9-8.el9_2.22024-04-15redhat
redhatbind-dyndb-ldap-0:11.9-7.el9_0.12024-04-15redhat
redhatunbound-0:1.7.3-17.el8_6.42024-04-15redhat
redhatbind-32:9.11.36-11.el8_9.12024-04-12redhat
redhatbind9.16-32:9.16.23-0.16.el8_9.22024-04-11redhat
redhatbind-dyndb-ldap-0:11.9-8.el9_3.32024-04-11redhat
redhatbind9.16-32:9.16.23-0.14.el8_8.42024-04-02redhat
redhatbind9.16-32:9.16.23-0.7.el8_6.52024-04-02redhat
redhatdnsmasq-0:2.79-21.el8_6.52024-03-27redhat
redhatdnsmasq-0:2.85-3.el9_0.12024-03-27redhat
redhatdnsmasq-0:2.79-26.el8_8.42024-03-27redhat
redhatdnsmasq-0:2.85-6.el9_2.32024-03-26redhat
redhatdnsmasq-0:2.79-31.el8_9.22024-03-14redhat
redhatdnsmasq-0:2.85-14.el9_3.12024-03-14redhat
redhatunbound-0:1.16.2-5.el8_8.12024-02-27redhat
redhatunbound-0:1.16.2-5.el8_9.22024-02-26redhat

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

(50 across 14 ecosystems)
Debian:12(7)
PackageVulnerable rangeFix by version rangeDependents
bind91:9.18.12-1 ... 1:9.18.24-1~bpo11+1 (8 versions)
  • every version up to 1:9.18.24-1: fixed in 1:9.18.24-1
—
dnsjava2.1.8-2, 3.6.2-1, 3.6.2-2, 3.6.3-1
  • every version on: no fix on record
—
dnsmasq2.89-1, 2.90-1, 2.90-2, 2.90-3
  • every version up to 2.90-4~deb12u1: fixed in 2.90-4~deb12u1
—
knot-resolver5.6.0-1
  • every version up to 5.6.0-1+deb12u1: fixed in 5.6.0-1+deb12u1
—
pdns-recursor4.8.4-1
  • every version up to 4.8.6-1: fixed in 4.8.6-1
—
systemd252.11-1 ... 252.6-1+loong64 (13 versions)
  • every version up to 252.23-1~deb12u1: fixed in 252.23-1~deb12u1
—
unbound1.17.1-2, 1.17.1-2+deb12u1
  • every version up to 1.17.1-2+deb12u2: fixed in 1.17.1-2+deb12u2
—
Debian:11(6)
PackageVulnerable rangeFix by version rangeDependents
bind91:9.16.15-1 ... 1:9.16.44-1~deb11u1 (11 versions)
  • every version up to 1:9.16.48-1: fixed in 1:9.16.48-1
—
dnsjava2.1.8-2, 3.6.2-1, 3.6.2-2, 3.6.3-1
  • every version on: no fix on record
—
dnsmasq2.85-1
  • every version up to 2.85-1+deb11u1: fixed in 2.85-1+deb11u1
—
knot-resolver5.3.1-1 ... 6.4.2-1 (43 versions)
  • every version on: no fix on record
—
pdns-recursor4.4.2-3 ... 5.4.5-1 (66 versions)
  • every version on: no fix on record
—
systemd247.3-6 ... 247.3-7+deb11u5 (7 versions)
  • every version up to 247.3-7+deb11u6: fixed in 247.3-7+deb11u6
—
Debian:13(6)
PackageVulnerable rangeFix by version rangeDependents
bind9—
  • every version up to 1:9.19.21-1: fixed in 1:9.19.21-1
—
dnsjava—
  • every version up to 3.6.2-1: fixed in 3.6.2-1
—
dnsmasq—
  • every version up to 2.90-1: fixed in 2.90-1
—
knot-resolver—
  • every version up to 5.7.1-1: fixed in 5.7.1-1
—
pdns-recursor—
  • every version up to 4.9.3-1: fixed in 4.9.3-1
—
systemd—
  • every version up to 255.4-1: fixed in 255.4-1
—
Debian:14(6)
PackageVulnerable rangeFix by version rangeDependents
bind9—
  • every version up to 1:9.19.21-1: fixed in 1:9.19.21-1
—
dnsjava—
  • every version up to 3.6.2-1: fixed in 3.6.2-1
—
dnsmasq—
  • every version up to 2.90-1: fixed in 2.90-1
—
knot-resolver—
  • every version up to 5.7.1-1: fixed in 5.7.1-1
—
pdns-recursor—
  • every version up to 4.9.3-1: fixed in 4.9.3-1
—
systemd—
  • every version up to 255.4-1: fixed in 255.4-1
—
Alpine:v3.17(3)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.0.0 up to 9.18.24-r0: fixed in 9.18.24-r0
—
dnsmasq—
  • every version up to 2.90-r0: fixed in 2.90-r0
—
unbound—
  • every version up to 1.19.1-r0: fixed in 1.19.1-r0
—
Alpine:v3.18(3)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.0.0 up to 9.18.24-r0: fixed in 9.18.24-r0
—
dnsmasq—
  • every version up to 2.90-r0: fixed in 2.90-r0
—
unbound—
  • every version up to 1.19.1-r0: fixed in 1.19.1-r0
—
Alpine:v3.19(3)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.0.0 up to 9.18.24-r0: fixed in 9.18.24-r0
—
dnsmasq—
  • every version up to 2.90-r0: fixed in 2.90-r0
—
unbound—
  • every version up to 1.19.1-r0: fixed in 1.19.1-r0
—
Alpine:v3.20(3)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.0.0 up to 9.18.24-r0: fixed in 9.18.24-r0
—
dnsmasq—
  • every version up to 2.90-r0: fixed in 2.90-r0
—
unbound—
  • every version up to 1.19.1-r0: fixed in 1.19.1-r0
—
Alpine:v3.21(3)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.0.0 up to 9.18.24-r0: fixed in 9.18.24-r0
—
dnsmasq—
  • every version up to 2.90-r0: fixed in 2.90-r0
—
unbound—
  • every version up to 1.19.1-r0: fixed in 1.19.1-r0
—
Alpine:v3.22(3)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.0.0 up to 9.18.24-r0: fixed in 9.18.24-r0
—
dnsmasq—
  • every version up to 2.90-r0: fixed in 2.90-r0
—
unbound—
  • every version up to 1.19.1-r0: fixed in 1.19.1-r0
—
Alpine:v3.23(3)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.0.0 up to 9.18.24-r0: fixed in 9.18.24-r0
—
dnsmasq—
  • every version up to 2.90-r0: fixed in 2.90-r0
—
unbound—
  • every version up to 1.19.1-r0: fixed in 1.19.1-r0
—
Alpine:v3.24(2)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.0.0 up to 9.18.24-r0: fixed in 9.18.24-r0
—
dnsmasq—
  • every version up to 2.90-r0: fixed in 2.90-r0
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.0.0 up to 9.16.48-r0: fixed in 9.16.48-r0
—
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
bind91:9.11.5.P4+dfsg-5.1 ... 1:9.11.5.P4+dfsg-5.1+deb10u9 (11 versions)
  • every version up to 1:9.11.5.P4+dfsg-5.1+deb10u11: fixed in 1:9.11.5.P4+dfsg-5.1+deb10u11
—

Weakness Classification(1)

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

Additional Vendor Advisories

(11)

Data Freshness Timeline

(refreshed 22× in last 7d / 63× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 90 of 109 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 10 repeat rows among the latest 100 are merged into the row they repeat. The 19 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 09:59 UTCEG score recompute
  2. 2026-11-02 09:59 UTCVendor advisory
  3. 2026-11-02 09:58 UTCGHSA enrichmentGHSA-8459-gg55-8qjj · GitHub severity HIGH · GitHub CVSS 7.5
  4. 2026-11-01 08:14 UTCEG score recompute
  5. 2026-11-01 08:14 UTCVendor advisory
  6. 2026-11-01 08:14 UTCGHSA enrichmentGHSA-8459-gg55-8qjj · GitHub severity HIGH · GitHub CVSS 7.5
  7. 2026-10-31 06:30 UTCEG score recompute
  8. 2026-10-31 06:30 UTCVendor advisory
  9. 2026-10-31 06:30 UTCGHSA enrichmentGHSA-8459-gg55-8qjj · GitHub severity HIGH · GitHub CVSS 7.5
  10. 2026-10-30 04:46 UTCEG score recompute
  11. 2026-10-30 04:46 UTCVendor advisory
  12. 2026-10-30 04:46 UTCGHSA enrichmentGHSA-8459-gg55-8qjj · GitHub severity HIGH · GitHub CVSS 7.5
  13. 2026-10-29 03:02 UTCEG score recompute
  14. 2026-10-29 03:02 UTCVendor advisory
  15. 2026-10-29 03:02 UTCGHSA enrichmentGHSA-8459-gg55-8qjj · GitHub severity HIGH · GitHub CVSS 7.5
  16. 2026-10-28 16:29 UTCEPSS rescoreEPSS >99.9% · 99th percentile
  17. 2026-10-28 01:18 UTCEG score recompute
  18. 2026-10-28 01:18 UTCVendor advisory
  19. 2026-10-28 01:18 UTCGHSA enrichmentGHSA-8459-gg55-8qjj · GitHub severity HIGH · GitHub CVSS 7.5
  20. 2026-10-26 23:30 UTCEG score recompute
  21. 2026-10-26 23:30 UTCVendor advisory
  22. 2026-10-26 23:29 UTCGHSA enrichmentGHSA-8459-gg55-8qjj · GitHub severity HIGH · GitHub CVSS 7.5
  23. 2026-10-25 18:14 UTCVendor advisory
  24. 2026-10-25 18:14 UTCGHSA enrichmentGHSA-8459-gg55-8qjj · GitHub severity HIGH · GitHub CVSS 7.5
  25. 2026-10-25 17:30 UTCEG score recompute
Show 65 more
  1. 2026-10-24 16:23 UTCEG score recompute
  2. 2026-10-24 16:23 UTCVendor advisory
  3. 2026-10-24 16:22 UTCGHSA enrichmentGHSA-8459-gg55-8qjj · GitHub severity HIGH · GitHub CVSS 7.5
  4. 2026-10-23 14:38 UTCEG score recompute
  5. 2026-10-23 14:38 UTCVendor advisory
  6. 2026-10-23 14:38 UTCGHSA enrichmentGHSA-8459-gg55-8qjj · GitHub severity HIGH · GitHub CVSS 7.5
  7. 2026-10-22 12:54 UTCEG score recompute
  8. 2026-10-22 12:54 UTCVendor advisory
  9. 2026-10-22 12:54 UTCGHSA enrichmentGHSA-8459-gg55-8qjj · GitHub severity HIGH · GitHub CVSS 7.5
  10. 2026-10-21 16:29 UTCEPSS rescoreEPSS >99.9% · 99th percentile
  11. 2026-10-21 11:09 UTCEG score recompute
  12. 2026-10-21 11:09 UTCVendor advisory
  13. 2026-10-21 11:09 UTCGHSA enrichmentGHSA-8459-gg55-8qjj · GitHub severity HIGH · GitHub CVSS 7.5
  14. 2026-10-20 09:25 UTCEG score recompute
  15. 2026-10-20 09:25 UTCVendor advisory
  16. 2026-10-20 09:25 UTCGHSA enrichmentGHSA-8459-gg55-8qjj · GitHub severity HIGH · GitHub CVSS 7.5
  17. 2026-10-19 07:40 UTCEG score recompute
  18. 2026-10-19 07:40 UTCVendor advisory
  19. 2026-10-19 07:40 UTCGHSA enrichmentGHSA-8459-gg55-8qjj · GitHub severity HIGH · GitHub CVSS 7.5
  20. 2026-10-18 05:56 UTCEG score recompute
  21. 2026-10-18 05:56 UTCVendor advisory
  22. 2026-10-18 05:56 UTCGHSA enrichmentGHSA-8459-gg55-8qjj · GitHub severity HIGH · GitHub CVSS 7.5
  23. 2026-10-17 04:11 UTCEG score recompute
  24. 2026-10-17 04:11 UTCVendor advisory
  25. 2026-10-17 04:11 UTCGHSA enrichmentGHSA-8459-gg55-8qjj · GitHub severity HIGH · GitHub CVSS 7.5
  26. 2026-10-16 02:24 UTCEG score recompute
  27. 2026-10-16 02:24 UTCVendor advisory
  28. 2026-10-16 02:24 UTCGHSA enrichmentGHSA-8459-gg55-8qjj · GitHub severity HIGH · GitHub CVSS 7.5
  29. 2026-10-14 22:21 UTCEG score recompute
  30. 2026-10-14 22:21 UTCVendor advisory
  31. 2026-10-14 22:21 UTCGHSA enrichmentGHSA-8459-gg55-8qjj · GitHub severity HIGH · GitHub CVSS 7.5
  32. 2026-10-13 18:01 UTCEG score recompute
  33. 2026-10-13 18:01 UTCVendor advisory
  34. 2026-10-13 18:00 UTCGHSA enrichmentGHSA-8459-gg55-8qjj · GitHub severity HIGH · GitHub CVSS 7.5
  35. 2026-10-12 16:16 UTCEG score recompute
  36. 2026-10-12 16:16 UTCVendor advisory
  37. 2026-10-12 16:16 UTCGHSA enrichmentGHSA-8459-gg55-8qjj · GitHub severity HIGH · GitHub CVSS 7.5
  38. 2026-10-11 21:40 UTCEG score recompute
  39. 2026-09-30 19:40 UTCOSV refresh
  40. 2026-09-30 16:35 UTCEG score recompute
  41. 2026-09-16 05:11 UTCEPSS rescoreEPSS >99.9% · 99th percentile
  42. 2026-09-12 02:23 UTCOSV refresh
  43. 2026-08-24 07:57 UTCOSV refresh
  44. 2026-08-08 04:19 UTCOSV refresh
  45. 2026-07-30 16:26 UTCEPSS rescoreEPSS >99.9% · 99th percentile
  46. 2026-07-24 14:16 UTCEPSS rescoreEPSS >99.9% · 99th percentile
  47. 2026-07-23 02:28 UTCEG score recompute
  48. 2026-07-22 21:23 UTCEG score recompute▲ 1.50
  49. 2026-07-22 21:23 UTCVendor advisory
  50. 2026-07-22 21:22 UTCGHSA enrichmentGHSA-8459-gg55-8qjj · GitHub severity HIGH · GitHub CVSS 7.5
  51. 2026-07-14 19:40 UTCOSV refresh
  52. 2026-07-08 15:13 UTCEPSS rescoreEPSS >99.9% · 99th percentile
  53. 2026-06-26 20:37 UTCOSV refresh
  54. 2026-06-15 17:47 UTCEPSS rescoreEPSS >99.9% · 99th percentile
  55. 2026-06-12 23:10 UTCEPSS rescoreEPSS 43% · 97th percentile
  56. 2026-06-11 13:59 UTCEPSS rescoreEPSS 43% · 97th percentile
  57. 2026-06-10 22:17 UTCEPSS rescoreEPSS 43% · 97th percentile
  58. 2026-06-10 13:21 UTCEPSS rescoreEPSS 43% · 97th percentile
  59. 2026-06-09 06:30 UTCOSV refresh
  60. 2026-06-08 14:16 UTCEPSS rescoreEPSS 44% · 97th percentile
  61. 2026-06-07 15:23 UTCEPSS rescoreEPSS 44% · 97th percentile
  62. 2026-06-06 13:46 UTCEPSS rescoreEPSS 44% · 97th percentile
  63. 2026-06-05 22:46 UTCEPSS rescoreEPSS 44% · 97th percentile
  64. 2026-06-05 06:09 UTCEPSS rescoreEPSS 44% · 97th percentile
  65. 2026-06-04 13:11 UTCEPSS rescoreEPSS 44% · 97th percentile

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • GitHub PoCknqyf263/CVE-2023-50387
    Published Feb 18, 2024

    KeyTrap (DNSSEC)

    Open source ↗

Frequently asked(5)

What is CVE-2023-50387?
CVE-2023-50387 is a critical-severity vulnerability; its CVE record was published on February 14, 2024. Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the "KeyTrap" issue. One of the concerns is that, when there is a zone with many DNSKEY and RRSIG…
When was the CVE record for CVE-2023-50387 published?
The CVE record for CVE-2023-50387 was published on February 14, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 4, 2025; the record at its source may have been updated since.
Is CVE-2023-50387 actively exploited?
CVE-2023-50387 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a >99.9% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-50387?
CVE-2023-50387 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
How do I remediate CVE-2023-50387?
A fix for CVE-2023-50387 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-50387 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-50387

Explore →

Is Your Infrastructure Affected by CVE-2023-50387?

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