CVE Intelligence
CISA KEV High exploit reference

CVE-2015-5477 — ISC BIND Data Processing Errors Vulnerability

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.

Published Jul 29, 2015 · Updated Oct 13, 2026 · Sources: CISA Known Exploited Vulnerabilities, NIST National Vulnerability Database, GitHub Security Advisories, CVE Program (cve.org) e CISA ADP · CNA: mitre

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

How the score was calculated
  • Confirmed exploitation (CISA KEV)+35
  • Public exploit/PoC (metasploit, exploitdb)+20
  • EPSS 99.4% (30-day exploitation probability)+15
  • Technical severity (high)+6
  • Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Confirmed
CISA KEV, listed Oct 8, 2026
EPSS FIRST
99.41%
ahead of 100% of scored CVEs · Oct 14, 2026
Affects
Apple
Os X Server and 20 more
CVSS base
7.5
High · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Active
none · proof-of-concept · active
Automatable
Yes
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented mitigation — kb.juniper.net (NIST National Vulnerability Database)
  • Documented patch — kb.isc.org (NIST National Vulnerability Database)

CISA required action CISA

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.

US federal deadline: Oct 11, 2026 — passed 4 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Apple Os X Server, Canonical Ubuntu Linux, Debian Debian Linux…).
  2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
  3. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  4. Apply the fixed version or the patch documented under Remediation.
  5. EPSS ahead of 100% of scored CVEs: prioritize it in the patch queue.
  6. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Apple Os X Server version 4.1.5 Vulnerable NIST National Vulnerability Database
Canonical Ubuntu Linux version 12.04 Vulnerable NIST National Vulnerability Database
Debian Debian Linux version 7.0version 8.0 Vulnerable NIST National Vulnerability Database
Fedoraproject Fedora version 21version 22 Vulnerable NIST National Vulnerability Database
Hp Hp-ux version 11.11version 11.23version 11.31 Vulnerable NIST National Vulnerability Database
Hp Openvms version 5.7 Vulnerable NIST National Vulnerability Database
Hpe Dns version 9.2.3version 9.3 Vulnerable NIST National Vulnerability Database
Hpe Vcx < 9.8.18 Vulnerable NIST National Vulnerability Database
Isc Bind version 9.10.2-p1≥ 9.10.0 and < 9.10.2≥ 9.1.0 and < 9.9.7 Vulnerable NIST National Vulnerability Database
Juniper Networks Junos < 12.1≥ 13.1 and < 13.2version 12.1version 12.1-r11version 12.1rversion 12.1x44version 12.1x44-d10version 12.1x44-d15
and 101 more version 12.1x44-d20version 12.1x44-d25version 12.1x44-d30version 12.1x44-d35version 12.1x44-d40version 12.1x44-d45version 12.1x44-d50version 12.1x45version 12.1x45-d10version 12.1x45-d15version 12.1x45-d20version 12.1x45-d30version 12.1x46version 12.1x46-d10version 12.1x46-d15version 12.1x46-d20version 12.1x46-d25version 12.1x46-d30version 12.1x46-d35version 12.1x47version 12.1x47-d10version 12.1x47-d15version 12.1x47-d20version 12.1x47-d25version 12.3version 12.3-r1version 12.3-r10version 12.3-r10-s1version 12.3-r10-s2version 12.3x48version 12.3x48-d10version 12.3x48-d15version 12.3x50version 12.3x50-d20version 12.3x50-d30version 12.3x50-d35version 12.3x50-d40version 12.3x50-d45version 13.2version 13.2-r1version 13.2-r2version 13.2-r3version 13.2-r4version 13.2-r5version 13.2-r6version 13.2-r7version 13.2-r7-s1version 13.2-r7-s2version 13.2-r8version 13.2x51version 13.2x51-d15version 13.2x51-d20version 13.2x51-d20.2version 13.2x51-d21version 13.2x51-d25version 13.2x51-d26version 13.2x51-d30version 13.2x51-d35version 14.1version 14.1-r1version 14.1-r2version 14.1-r3version 14.1-r4version 14.1-r5version 14.1x50version 14.1x50-d60version 14.1x51version 14.1x51-d60version 14.1x53version 14.1x53-d10version 14.1x53-d15version 14.1x53-d16version 14.1x53-d20version 14.1x53-d25version 14.1x53-d26version 14.1x53-d27version 14.1x53-r1version 14.2version 14.2-rversion 14.2-r1version 14.2-r2version 14.2-r3version 14.2-r4version 15.1version 15.1-a1version 15.1-fversion 15.1-f1version 15.1-f2version 15.1-f2-s1version 15.1-f2-s2version 15.1-f2-s3version 15.1-f2-s4version 15.1-rversion 15.1-r1version 15.1x49version 15.1x49-d10version 15.1x49-d15version 15.1x49-d20version 15.1x49-d25version 15.1x53version 15.1x53-d10
Vulnerable NIST National Vulnerability Database
Netapp Clustered Data Ontap versions not specified by the source Vulnerable NIST National Vulnerability Database
Opensuse Evergreen version 11.4 Vulnerable NIST National Vulnerability Database
Opensuse Opensuse version 13.1version 13.2 Vulnerable NIST National Vulnerability Database
Oracle Solaris version 11.2version 10 Vulnerable NIST National Vulnerability Database
Oracle Vm Server version 3.2 Vulnerable NIST National Vulnerability Database
Red Hat Enterprise Linux version 5.0version 6.0version 7.0 Vulnerable NIST National Vulnerability Database
Red Hat Enterprise Linux Aus version 6.4version 6.5version 6.6 Vulnerable NIST National Vulnerability Database
SUSE Linux Enterprise Debuginfo version 11-sp4version 11-sp3 Vulnerable NIST National Vulnerability Database
SUSE Linux Enterprise Desktop version 11-sp4version 12version 11-sp3 Vulnerable NIST National Vulnerability Database
SUSE Linux Enterprise Server version 10-sp4version 11-sp1version 11-sp2version 11-sp3version 11-sp4version 12 Vulnerable NIST National Vulnerability Database
SUSE Linux Enterprise Software Development Kit version 11-sp3version 11-sp4version 12 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.5 CVSS 3.1 High 3.9 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
7.5 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
7.5 CVSS 3.1 High — — CISA-ADP via CVE Program (cve.org) e CISA ADP
7.8 CVSS 2.0 High 10.0 6.9 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (score shown at the top: 134c704f-9b21-4f2e-91b3-4a467353bcc0)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-19

Other CVEs with this weakness →

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

Listed
Oct 8, 2026
Federal deadline
Oct 11, 2026
passed 4 day(s) ago
Ransomware use
Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

Public exploits, PoCs and detection templates

Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.

Metasploit modules

Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 99.41%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Hunt retroactively in logs from before Oct 8, 2026 (KEV listing): exploitation may have started earlier.
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • Affected products added · juniper/junos, fedoraproject/fedora, redhat/enterprise linux, redhat/enterprise linux aus, debian/debian linux, oracle/v
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 7.5
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Added to CISA KEV (detected)
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Record created in this database
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Added to CISA KEV catalog
    Oct 7, 2026 · CISA
  • 2015
  • CVE published
    Jul 29, 2015 · mitre

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

48 on the record

Elsewhere on this site

Apple
every CVE for this vendor
2026-10
what else CISA listed that month
CWE-19
other pages naming this weakness

Related CVEs (same products)

  • Medium CVE-2026-104046 Sssd: sssd: denial of service via incomplete identity provider authentication requests 8d
  • Medium CVE-2026-104045 Sssd: sssd: denial of service via race condition in autofs responder 8d
  • High CVE-2026-104048 Sssd: sssd: authorization bypass via cross-domain username collision in hbac evaluation 8d
  • Medium CVE-2026-104047 Sssd: sssd: information disclosure via query injection in entra id lookups 8d
  • High CVE-2026-102558 Libsoup: libsoup: heap buffer overflow during websocket receive-buffer growth 16d
  • High CVE-2026-102555 Libsoup: libsoup: heap buffer overflow via uninitialized length in data-uri base64 decoding 16d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2015-5477 is "ISC BIND Data Processing Errors Vulnerability", rated High. It affects Os X Server (Apple); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 7.5 describes technical severity. EPSS 99.41% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.