CVE-2015-5477
Exploited in the wild. In CISA KEV since 2026‑10‑08. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- Juniper JunosAffected: < 12.1Upgrade to: 12.1Stated by: NVD
- Hpe VcxAffected: < 9.8.18Upgrade to: 9.8.18Stated by: NVD
- Isc BindAffected: ≥ 9.1.0, < 9.9.7Upgrade to: 9.9.7Stated by: NVD
Versions as the sources state them. Full version matrix after sign-in
Steps
Written by AI from the record- Check whether your business runs its own BIND DNS server (versions before 9.9.7-P2 or before 9.10.2-P3) — most small businesses use a hosting provider's or registrar's DNS and are not affected.
- If you or your IT provider manage BIND directly, ask them to confirm the exact version running.
- Upgrade to BIND 9.9.7-P2 or 9.10.2-P3 (or later) immediately.
- If patching can't happen right away, restrict which networks can send DNS queries to the server until it's updated.
- Confirm with your IT provider that the fix has been applied by the CISA deadline of 2026-10-11.
Coverage timeline
1 publisherAdvisory coverage
Added to CISA KEV catalog
Sourced from public security reporting — each date is when it was published, not when it happened. 2 further articles named this CVE in wider roundups without reporting it as a distinct event.
What it is
From the CVE record
named in ISC BIND 9.x before 9.9.7-P2 and 9.10.x before 9.10.2-P3 allows remote attackers to cause a denial of service (REQUIRE assertion failure and daemon exit) via TKEY queries.
In plain language
Written by AI from the recordA core piece of software that runs the internet's address book (BIND DNS server) can be crashed remotely by attackers sending it a special query, and this is already being actively exploited — if you run your own DNS server on BIND, you need to patch it now.
Remotely triggerable REQUIRE assertion failure in ISC BIND's named daemon via crafted TKEY queries causes a denial-of-service crash, and CISA confirms active exploitation in the wild.
If you're affected
- Website/email downtime
- DNS resolution outage
- Operational disruption
- Customer-facing service loss
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Listed as exploited in the wild since 2026-10-08.
US federal agencies must remediate by 2026-10-11.
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
- Public exploits
3 sources with a proof of concept or module.
Exploit links, PoCs and Metasploit modules after sign-in- EPSS
99% chance of exploitation activity in the next 30 days, which ranks it in the 99th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
- Attention now
Sustained, driven by in-the-wild reports.
Lifecycle
A public exploit existed 61 days before the patch.
- Patch availablepatch available, workaround available, record updated, record updated
- Added to CISA KEVpatch available, record updated
- OpenVAS check added
- Patch availablerecord updated
- Public exploit / PoCsource: exploit-db
- Publishedweakness classified, att&ck mapped
Affected products
And 8 more affected products. See all after sign-in
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Scored 7.5 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality NoneNo confidentiality impact
- Integrity NoneNo integrity impact
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
Sources
References in the record
- packetstormsecurity.com/files/132926/BIND-TKEY-Query-Denial-Of-Service.html
- oracle.com/technetwork/topics/security/ovmbulletinjul2016-3090546.html
- lists.opensuse.org/opensuse-security-announce/2015-07/msg00050.html
And 40 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next exploited one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Suse, not every advisory. This one: actively exploited.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI