BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-11411High confidence

Possible domain hijacking via promiscuous records in the authority section

NLnet Labs · Unbound

5.7MediumCVSS 4.0
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.33% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs NLnet Labs Unbound and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Alpine, Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

8 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · mainunboundVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.1.24.1-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.22v3.22 · mainunboundVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.1.23.1-r1Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.21v3.21 · mainunboundVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.1.22.0-r1Alpine Security Database ↗Source updated 3 Oct 2026
Debian trixietrixie · sourceunboundVendor fix publishedDebian records a fixed source-package version for this release.1.22.0-2+deb13u1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourceunboundVendor fix publishedDebian records a fixed source-package version for this release.1.17.1-2+deb12u4Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourceunboundVendor fix publishedDebian records a fixed source-package version for this release.1.24.2-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourceunboundVendor fix publishedDebian records a fixed source-package version for this release.1.24.2-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archiveunboundVendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.1.19.2-1ubuntu3.7Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2025-11411 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityunbound: Unbound domain hijacking via promiscuous records
17 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • unbound as a component of Red Hat Enterprise Linux 6
  • unbound-devel as a component of Red Hat Enterprise Linux 6
  • unbound-libs as a component of Red Hat Enterprise Linux 6
  • unbound-python as a component of Red Hat Enterprise Linux 6
  • unbound.src as a component of Red Hat Enterprise Linux 6
  • unbound as a component of Red Hat Enterprise Linux 7
  • unbound-devel as a component of Red Hat Enterprise Linux 7
  • unbound-libs as a component of Red Hat Enterprise Linux 7
  • unbound-python as a component of Red Hat Enterprise Linux 7
  • unbound.src as a component of Red Hat Enterprise Linux 7
  • python3-unbound as a component of Red Hat Enterprise Linux 8
  • unbound as a component of Red Hat Enterprise Linux 8
Summary
A domain hijacking flaw has been discovered in NLNet Lab's Unbound project. Promiscuous NS RRSets that complement positive DNS replies in the authority section can be used to trick resolvers to update their delegation information for the zone. Usually these RRSets are used to update the resolver's knowledge of the zone's name servers. A malicious actor can exploit the possible poisonous effect by injecting NS RRSets (and possibly their respective address records) in a reply. This could be done for example by trying to spoof a packet or fragmentation attacks. Unbound would then proceed to update the NS RRSet data it already has since the new data has enough trust for it, i.e., in-zone data for the delegation point.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-35360

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

NLnet Labs Unbound up to and including version 1.24.1 is vulnerable to possible domain hijack attacks. Promiscuous NS RRSets that complement positive DNS replies in the authority section can be used to trick resolvers to update their delegation information for the zone. Usually these RRSets are used to update the resolver's knowledge of the zone's name servers. A malicious actor can exploit the possible poisonous effect by injecting NS RRSets (and possibly their respective address records) in a reply. This could be done for example by trying to spoof a packet or fragmentation attacks. Unbound would then proceed to update the NS RRSet data it already has since the new data has enough trust for it, i.e., in-zone data for the delegation point. Unbound 1.24.1 includes a fix that scrubs unsolicited NS RRSets (and their respective address records) from replies mitigating the possible poison effect. Unbound 1.24.2 includes an additional fix that scrubs unsolicited NS RRSets (and their respective address records) from YXDOMAIN and non-referral nodata replies, further mitigating the possible poison effect.

What

NLnet Labs Unbound up to and including version 1.24.1 is vulnerable to possible domain hijack attacks. Promiscuous NS RRSets that complement positive DNS replies in the authority section can be used to trick resolvers to update their delegation information for the zone. Usually these RRSets are used to update the resolver's knowledge of the zone's name servers. A malicious actor can exploit the possible poisonous effect by injecting NS RRSets (and possibly their respective address records) in a reply. This could be done for example by trying to spoof a packet or fragmentation attacks. Unbound would then proceed to update the NS RRSet data it already has since the new data has enough trust for it, i.e., in-zone data for the delegation point. Unbound 1.24.1 includes a fix that scrubs unsolicited NS RRSets (and their respective address records) from replies mitigating the possible poison effect. Unbound 1.24.2 includes an additional fix that scrubs unsolicited NS RRSets (and their respective address records) from YXDOMAIN and non-referral nodata replies, further mitigating the possible poison effect.

Why

The product, when processing trusted data, accepts any untrusted data that is also included with the trusted data, treating the untrusted data as if it were trusted.

How

An attacker operating through an adjacent network may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

NLnet Labs Unbound up to and including version 1.24.1 is vulnerable to possible domain hijack attacks. Promiscuous NS RRSets that complement positive DNS replies in the authority section can be used to trick resolvers to update their delegation information for the zone. Usually these RRSets are used to update the resolver's knowledge of the zone's name servers. A malicious actor can exploit the possible poisonous effect by injecting NS RRSets (and possibly their respective address records) in a reply. This could be done for example by trying to spoof a packet or fragmentation attacks. Unbound would then proceed to update the NS RRSet data it already has since the new data has enough trust for it, i.e., in-zone data for the delegation point. Unbound 1.24.1 includes a fix that scrubs unsolicited NS RRSets (and their respective address records) from replies mitigating the possible poison effect. Unbound 1.24.2 includes an additional fix that scrubs unsolicited NS RRSets (and their respective address records) from YXDOMAIN and non-referral nodata replies, further mitigating the possible poison effect.

Why

The product, when processing trusted data, accepts any untrusted data that is also included with the trusted data, treating the untrusted data as if it were trusted.

How

An attacker operating through an adjacent network may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
an adjacent network → Acceptance of Extraneous Untrusted Data With Trusted Data → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Adjacent
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-349 ↗

CWE-349: Acceptance of Extraneous Untrusted Data With Trusted Data. The product, when processing trusted data, accepts any untrusted data that is also included with the trusted data, treating the untrusted data as if it were trusted.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:H/E:P

Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.

AVAdjacentAttack vector: The attacker must be on an adjacent or logically close network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATPresentAttack requirements: A particular deployment or execution condition must be present.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.VCNoneVulnerable-system confidentiality: No direct loss is represented by this metric.VIHighVulnerable-system integrity: A successful attack can cause a major loss.VANoneVulnerable-system availability: No direct loss is represented by this metric.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SIHighSubsequent-system integrity: A successful attack can cause a major loss.SAHighSubsequent-system availability: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
UnauthenticatedCWE-349
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-0489Xerox FreeFlow Print Server: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Xerox FreeFlow Print Server ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-0413Securepoint UTM: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Komponenten von Drittanbietern in Securepoint UTM ausnutzen, um Dateien zu manipulieren, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.manipulieren.

Official advisory ↗
BSI · German · WID-SEC-2025-2386Unbound: Schwachstelle ermöglicht Manipulation von Dateien

Ein Angreifer aus einem angrenzenden Netzwerk kann eine Schwachstelle in Unbound ausnutzen, um den Cache zu manipulieren, was möglicherweise zu Domain-Hijacking führen kann.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20251029Security Bulletin 29 Oct 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 29 Oct 2025, published on 29 October 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0969Multiples vulnérabilités dans les produits VMware

rg/CVERecord?id=CVE-2025-0395 Référence CVE CVE-2025-0725 https://www.cve.org/CVERecord?id=CVE-2025-0725 Référence CVE CVE-2025-0838 https://www.cve.org/CVERecord?id=CVE-2025-0838 Référence CVE CVE-2025-0913 https://www.cve.org/CVERecord?id=CVE-2025-0913 Référence CVE CVE-2025-0938 https://www.cve.org/CVERecord?id=CVE-2025-0938 Référence CVE CVE-2025-10148 https://www.cve.org/CVERecord?id=CVE-2025-10148 Référence CVE CVE-2025-10911 https://www.cve.org/CVERecord?id=CVE-2025-10911 Référence CVE CVE-2025-1094 https://www.cve.org/CVERecord?id=CVE-2025-1094 Référence CVE CVE-2025-11226 https://www.cve.org/CVERecord?id=CVE-2025-11226 Référence CVE CVE-2025-11411 https://www.cve.org/CVERecord?id=CVE-2025-11411 Référence CVE CVE-2025-11731 https://www.cve.org/CVERecord?id=CVE-2025-11731 Référence CVE CVE-2025-1215 https://www.cve.org/CVERecord?id=CVE-2025-1215 Référence CVE CVE-2025-12380 https://www.cve.org/CVERecord?id=CVE-2025-12380 Référence CVE CVE-2025-1352 https://www.cve.org/CVERecord?id=CVE-2025-1352 Référence CVE CVE-2025-1365 https://www.cve.org/CVERecord?id=CVE-2025-1365 Référence CVE CVE-2025-1371 https://www.cve.org/CVERecord?id=CVE-2025-1371 Référence CVE CVE-2025-1372 https://www.cve.org/CVERecord?id=CVE-2025-1372 Référence CVE CVE-2025-1376 https://www.cve.org/CVERecord?id=CVE-2025-13

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0920Multiples vulnérabilités dans les produits Microsoft

CVE-2025-53045 du 23 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-53053 du 23 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-53054 du 23 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-53062 du 23 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-53069 du 23 octobre 2025 Bulletin de sécurité Microsoft CVE-2022-49469 du 24 octobre 2025 Bulletin de sécurité Microsoft CVE-2022-49552 du 24 octobre 2025 Bulletin de sécurité Microsoft CVE-2022-49562 du 24 octobre 2025 Bulletin de sécurité Microsoft CVE-2022-49610 du 24 octobre 2025 Bulletin de sécurité Microsoft CVE-2022-49635 du 24 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-11411 du 24 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-62813 du 24 octobre 2025 Une gestion de version détaillée se trouve à la fin de ce document. Risque Non spécifié par l'éditeur Systèmes affectés azl3 lz4 1.9.4-1 azl3 mysql versions antérieures à 8.0.44-1 azl3 squid versions antérieures à 6.13-3 azl3 unbound 1.19.1-4 cbl2 kernel 5.15.186.1-1 cbl2 mysql 8.0.43-1 Résumé De multiples vulnérabilités ont été découvertes dans les produits Microsoft. Elles permettent à un attaquant de provoquer un problème de sécurité non spécifié par l'éditeur. Solutions Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. s

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Fixed
Action
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 22 Oct 2025 · Last source change 5 Dec 2025, 10:56 UTC · CWE-349 · Acceptance of Extraneous Untrusted Data With Trusted Data

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-35360
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD not scheduled

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    ≤ 1.24.1 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    ≤ 1.24.1 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    unbound as a component of Red Hat Enterprise Linux 6; unbound-devel as a component of Red Hat Enterprise Linux 6; unbound-libs as a component of Red Hat Enterprise Linux 6; unbound-python as a component of Red Hat Enterprise Linux 6; unbound.src as a component of Red Hat Enterprise Linux 6; unbound as a component of Red Hat Enterprise Linux 7; unbound-devel as a component of Red Hat Enterprise Linux 7; unbound-libs as a component of Red Hat Enterprise Linux 7; unbound-python as a component of Red Hat Enterprise Linux 7; unbound.src as a component of Red Hat Enterprise Linux 7; python3-unbound as a component of Red Hat Enterprise Linux 8; unbound as a component of Red Hat Enterprise Linux 8; unbound-devel as a component of Red Hat Enterprise Linux 8; unbound-libs as a component of Red Hat Enterprise Linux 8; unbound.src as a component of Red Hat Enterprise Linux 8; openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4 · Fixed: python3-unbound-0:1.24.2-7.el10.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); python3-unbound-0:1.24.2-7.el10.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); python3-unbound-0:1.24.2-7.el10.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); python3-unbound-0:1.24.2-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); python3-unbound-debuginfo-0:1.24.2-7.el10.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); python3-unbound-debuginfo-0:1.24.2-7.el10.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); python3-unbound-debuginfo-0:1.24.2-7.el10.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); python3-unbound-debuginfo-0:1.24.2-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-0:1.24.2-7.el10.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-0:1.24.2-7.el10.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-0:1.24.2-7.el10.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-0:1.24.2-7.el10.src as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-0:1.24.2-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-anchor-0:1.24.2-7.el10.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-anchor-0:1.24.2-7.el10.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-anchor-0:1.24.2-7.el10.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-anchor-0:1.24.2-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-anchor-debuginfo-0:1.24.2-7.el10.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-anchor-debuginfo-0:1.24.2-7.el10.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-anchor-debuginfo-0:1.24.2-7.el10.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-anchor-debuginfo-0:1.24.2-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-debuginfo-0:1.24.2-7.el10.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-debuginfo-0:1.24.2-7.el10.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-debuginfo-0:1.24.2-7.el10.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-debuginfo-0:1.24.2-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-debugsource-0:1.24.2-7.el10.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-debugsource-0:1.24.2-7.el10.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-debugsource-0:1.24.2-7.el10.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-debugsource-0:1.24.2-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-dracut-0:1.24.2-7.el10.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); and 114 more
    After
    unbound as a component of Red Hat Enterprise Linux 6; unbound-devel as a component of Red Hat Enterprise Linux 6; unbound-libs as a component of Red Hat Enterprise Linux 6; unbound-python as a component of Red Hat Enterprise Linux 6; unbound.src as a component of Red Hat Enterprise Linux 6; unbound as a component of Red Hat Enterprise Linux 7; unbound-devel as a component of Red Hat Enterprise Linux 7; unbound-libs as a component of Red Hat Enterprise Linux 7; unbound-python as a component of Red Hat Enterprise Linux 7; unbound.src as a component of Red Hat Enterprise Linux 7; python3-unbound as a component of Red Hat Enterprise Linux 8; unbound as a component of Red Hat Enterprise Linux 8; unbound-devel as a component of Red Hat Enterprise Linux 8; unbound-libs as a component of Red Hat Enterprise Linux 8; unbound.src as a component of Red Hat Enterprise Linux 8; openshift/ose-rhel-coreos-8 as a component of Red Hat OpenShift Container Platform 4; openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4 · Fixed: python3-unbound-0:1.24.2-7.el10.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); python3-unbound-0:1.24.2-7.el10.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); python3-unbound-0:1.24.2-7.el10.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); python3-unbound-0:1.24.2-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); python3-unbound-debuginfo-0:1.24.2-7.el10.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); python3-unbound-debuginfo-0:1.24.2-7.el10.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); python3-unbound-debuginfo-0:1.24.2-7.el10.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); python3-unbound-debuginfo-0:1.24.2-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-0:1.24.2-7.el10.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-0:1.24.2-7.el10.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-0:1.24.2-7.el10.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-0:1.24.2-7.el10.src as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-0:1.24.2-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-anchor-0:1.24.2-7.el10.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-anchor-0:1.24.2-7.el10.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-anchor-0:1.24.2-7.el10.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-anchor-0:1.24.2-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-anchor-debuginfo-0:1.24.2-7.el10.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-anchor-debuginfo-0:1.24.2-7.el10.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-anchor-debuginfo-0:1.24.2-7.el10.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-anchor-debuginfo-0:1.24.2-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-debuginfo-0:1.24.2-7.el10.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-debuginfo-0:1.24.2-7.el10.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-debuginfo-0:1.24.2-7.el10.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-debuginfo-0:1.24.2-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-debugsource-0:1.24.2-7.el10.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-debugsource-0:1.24.2-7.el10.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-debugsource-0:1.24.2-7.el10.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-debugsource-0:1.24.2-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); unbound-dracut-0:1.24.2-7.el10.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); and 114 more
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2025-35360↗Red Hat Product Security security advisory↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-11411 · cve.blacktree.nl