VulnerabilityPublished 12 Nov 2025Updated 20 Nov 2025

CVE-2025-59088: Important · idm:DL1 security update

Affects bind-dyndb-ldapSource GCVE Database

Compare

Mentioned vulnerabilities

CVE-2025-59089

Authoritative record:CVE-2025-59088· High 8.6

Not known to be exploited · CVSS 8.6 High · fixed in 11.6-6.module_el8.10.0+3980+d78e8e90 : patch bind-dyndb-ldap soon.

Data as of 13 Nov 2026, 18:29 UTC

CVSS 3.1 base score

8.6High

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (redhat)	CVSS 3.1	8.6

Patch: Available – fixed in 11.6-6.module_el8.10.0+3980+d78e8e90, 0.6.0-3.module_el8.6.0+2881+2f24dc92, 4.9.13-20.module_el8.10.0+4050+3b475c71 +10

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

almalinux-8

What to do

Upgrade to a fixed release listed under Affected software.

Patches and advisories

access.redhat.com/errata/RHSA-2025:21140 (opens in a new tab)

Affected software

Product	Affected	Fixed in
AlmaLinux 8bind-dyndb-ldap	Affected <11.6-6.module_el8.10.0+3980+d78e8e90	Fixed in 11.6-6.module_el8.10.0+3980+d78e8e90
AlmaLinux 8custodia	Affected <0.6.0-3.module_el8.6.0+2881+2f24dc92	Fixed in 0.6.0-3.module_el8.6.0+2881+2f24dc92
AlmaLinux 8ipa-client	Affected <4.9.13-20.module_el8.10.0+4050+3b475c71	Fixed in 4.9.13-20.module_el8.10.0+4050+3b475c71
AlmaLinux 8ipa-client-common	Affected <4.9.13-20.module_el8.10.0+4050+3b475c71	Fixed in 4.9.13-20.module_el8.10.0+4050+3b475c71
AlmaLinux 8ipa-client-epn	Affected <4.9.13-20.module_el8.10.0+4050+3b475c71	Fixed in 4.9.13-20.module_el8.10.0+4050+3b475c71
AlmaLinux 8ipa-client-samba	Affected <4.9.13-20.module_el8.10.0+4050+3b475c71	Fixed in 4.9.13-20.module_el8.10.0+4050+3b475c71

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

AlmaLinux Identity Management (IdM) is a centralized authentication, identity management, and authorization solution for both traditional and cloud-based enterprise environments. Security Fix(es): * python-kdcproxy: Unauthenticated SSRF via Realm?Controlled DNS SRV (CVE-2025-59088) * python-kdcproxy: Remote DoS via unbounded TCP upstream buffering (CVE-2025-59089) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

References

Community reviews

Loading reviews…