BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-18922High confidence

389-ds-base: 389-ds-base: sasl plain authentication allows privilege escalation to directory manager via stale identity in cyrus sasl auxiliary property

Red Hat · Red Hat Directory Server 11.5 E4S for RHEL 8

Official source article: Red Hat RHSA-2026:64771 ↗. Check the applicable product and release in the original source.

9.8CriticalCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 3 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.56% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Red Hat Red Hat Directory Server 11.5 E4S for RHEL 8 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: Within 3 daysRemediation target: Within 90 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.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 3 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

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

4 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 3 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

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
Debian trixietrixie · source389-ds-baseAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 4 Nov 2026
Debian bookwormbookworm · source389-ds-baseAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 4 Nov 2026
Debian sidsid · source389-ds-baseAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 4 Nov 2026
Ubuntu 24.04 LTSnoble · standard archive389-ds-baseUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 4 Nov 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-2026-18922 · CSAF 2.0 · revision 3 · finalRed Hat Product Security389-ds-base: 389-ds-base: SASL PLAIN authentication allows privilege escalation to Directory Manager via stale identity in Cyrus SASL auxiliary property
1 known affected

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

  • 389-ds-base.src as a component of Red Hat Directory Server 12
Summary
A flaw was found in 389 Directory Server. During SASL PLAIN authentication, a stale identity carried in a Cyrus SASL auxiliary property from a prior failed bind attempt can be installed on a connection following a subsequent, unrelated successful bind, regardless of which SASL mechanism completes that second bind. An attacker can send a SASL PLAIN bind as cn=Directory Manager with an incorrect password, then complete a SASL ANONYMOUS bind on the same connection, causing the server to grant Directory Manager authority without any valid credentials. A variant using a valid low-privileged account's own successful bind instead of an anonymous one is also possible.
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-2026-72457

No EUVD known-exploited evidence

A flaw was found in 389 Directory Server. During SASL PLAIN authentication, a stale identity carried in a Cyrus SASL auxiliary property from a prior failed bind attempt can be installed on a connection following a subsequent, unrelated successful bind, regardless of which SASL mechanism completes that second bind. An attacker can send a SASL PLAIN bind as cn=Directory Manager with an incorrect password, then complete a SASL ANONYMOUS bind on the same connection, causing the server to grant Directory Manager authority without any valid credentials. A variant using a valid low-privileged account's own successful bind instead of an anonymous one is also possible.

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
9.8 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 3 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

A flaw was found in 389 Directory Server. During SASL PLAIN authentication, a stale identity carried in a Cyrus SASL auxiliary property from a prior failed bind attempt can be installed on a connection following a subsequent, unrelated successful bind, regardless of which SASL mechanism completes that second bind. An attacker can send a SASL PLAIN bind as cn=Directory Manager with an incorrect password, then complete a SASL ANONYMOUS bind on the same connection, causing the server to grant Directory Manager authority without any valid credentials. A variant using a valid low-privileged account's own successful bind instead of an anonymous one is also possible.

What

A flaw was found in 389 Directory Server. During SASL PLAIN authentication, a stale identity carried in a Cyrus SASL auxiliary property from a prior failed bind attempt can be installed on a connection following a subsequent, unrelated successful bind, regardless of which SASL mechanism completes that second bind. An attacker can send a SASL PLAIN bind as cn=Directory Manager with an incorrect password, then complete a SASL ANONYMOUS bind on the same connection, causing the server to grant Directory Manager authority without any valid credentials. A variant using a valid low-privileged account's own successful bind instead of an anonymous one is also possible.

Why

The affected component does not establish the requesting party's identity reliably before granting access.

How

An attacker operating through a network path 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

A flaw was found in 389 Directory Server. During SASL PLAIN authentication, a stale identity carried in a Cyrus SASL auxiliary property from a prior failed bind attempt can be installed on a connection following a subsequent, unrelated successful bind, regardless of which SASL mechanism completes that second bind. An attacker can send a SASL PLAIN bind as cn=Directory Manager with an incorrect password, then complete a SASL ANONYMOUS bind on the same connection, causing the server to grant Directory Manager authority without any valid credentials. A variant using a valid low-privileged account's own successful bind instead of an anonymous one is also possible.

Why

The affected component does not establish the requesting party's identity reliably before granting access.

How

An attacker operating through a network path 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
a network path → Improper Authentication → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-287 ↗

CWE-287: Improper Authentication. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
Stolen credentials, tokens and legitimate administration functions may provide continued access without deploying a large custom toolset.
NetworkUnauthenticatedCWE-287
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-72457Official EUVD mapping

A flaw was found in 389 Directory Server. During SASL PLAIN authentication, a stale identity carried in a Cyrus SASL auxiliary property from a prior failed bind attempt can be installed on a connection following a subsequent, unrelated successful bind, regardless of which SASL mechanism completes that second bind. An attacker can send a SASL PLAIN bind as cn=Directory Manager with an incorrect password, then complete a SASL ANONYMOUS bind on the same connection, causing the server to grant Directory Manager authority without any valid credentials. A variant using a valid low-privileged account's own successful bind instead of an anonymous one is also possible.

Official EUVD record ↗
BSI · German · WID-SEC-2026-3215Red Hat Directory Server und Enterprise Linux (389-ds-base): Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Red Hat Directory Server und Red Hat Enterprise Linux ausnutzen, um beliebigen Code auszuführen, Administratorrechte zu erlangen, Daten zu manipulieren oder einen Denial-of-Service-Zustand auszulösen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260909Security Bulletin 9 Sep 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 9 Sep 2026, published on 9 September 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

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.
Fix availability varies by product
Affected
389-ds-base.src as a component of Red Hat Directory Server 12
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 7 Sept 2026 · Last source change 8 Oct 2026, 14:14 UTC · CWE-287 · Improper Authentication

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-09-09
European sourceENISA EUVD · EUVD-2026-72457
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD awaiting enrichment

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: added remediation: access.redhat.com/RHSA-2026:64771; removed remediation: access.redhat.com/RHSA-2026:79217; removed vendor advisory: access.redhat.com/RHSA-2026:79217.
    Before
    remediation: access.redhat.com/RHSA-2026:79217 · vendor advisory: access.redhat.com/RHSA-2026:79217
    After
    remediation: access.redhat.com/RHSA-2026:64771
    CNA ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: added remediation: access.redhat.com/RHSA-2026:79217; added vendor advisory: access.redhat.com/RHSA-2026:79217; removed remediation: access.redhat.com/RHSA-2026:64771.
    Before
    remediation: access.redhat.com/RHSA-2026:64771
    After
    remediation: access.redhat.com/RHSA-2026:79217 · vendor advisory: access.redhat.com/RHSA-2026:79217
    access.redhat.com ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    See the vendor and CVE records for the affected range. · Fixed: 8080020260903102346.f969626e < *; 8100020260904171440.37ed7c03 < *; 9020020260903155914.1674d574 < *; 9040020260903102623.1674d574 < *; 0:3.2.0-10.el10_2 < *; 0:3.0.6-21.el10_0 < *; 0:1.2.11.15-97.el6_10.1 < *; 0:1.3.11.1-15.el7_9 < *
    After
    See the vendor and CVE records for the affected range. · Fixed: Red Hat Directory Server 11.5 E4S for RHEL 8: 8060020260908152739.0ca98e7e < *; Red Hat Directory Server 11.7 E4S for RHEL 8: 8080020260903102346.f969626e < *; Red Hat Directory Server 11.9 for RHEL 8: 8100020260904171440.37ed7c03 < *; Red Hat Directory Server 12.2 E4S for RHEL 9: 9020020260903155914.1674d574 < *; Red Hat Directory Server 12.4 E4S for RHEL 9: 9040020260903102623.1674d574 < *; Red Hat Enterprise Linux 10: 0:3.2.0-10.el10_2 < *; Red Hat Enterprise Linux 10.0 Extended Update Support: 0:3.0.6-21.el10_0 < *; Red Hat Enterprise Linux 6 Extended Lifecycle Support - EXTENSION: 0:1.2.11.15-97.el6_10.1 < *; Red Hat Enterprise Linux 7 Extended Lifecycle Support: 0:1.3.11.1-15.el7_9 < *; Red Hat Enterprise Linux 8: 8100020260904155442.25e700aa < *; Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support: 8040020260901171549.96015a92 < *; Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On: 8040020260901171549.96015a92 < *; Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support: 8060020260901145727.824efc52 < *; Red Hat Enterprise Linux 8.6 Extended Update Support Long-Life Add-On: 8060020260901145727.824efc52 < *; Red Hat Enterprise Linux 8.8 Telecommunications Update Service: 8080020260831180218.6dbb3803 < *; Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions: 8080020260831180218.6dbb3803 < *; Red Hat Enterprise Linux 9: 0:2.8.0-10.el9_8 < *; Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions: 0:2.2.4-22.el9_2 < *; Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions: 0:2.4.5-29.el9_4 < *; Red Hat Enterprise Linux 9.6 Extended Update Support: 0:2.6.1-24.el9_6 < *
    CNA ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    389-ds-base.src as a component of Red Hat Directory Server 12 · Fixed: 389-ds-base-0:1.2.11.15-97.el6_10.1.i686 as a component of Red Hat Enterprise Linux Server -EXTENSION(v. 6 ELS-EXTENSION); 389-ds-base-0:1.2.11.15-97.el6_10.1.src as a component of Red Hat Enterprise Linux Server -EXTENSION(v. 6 ELS-EXTENSION); 389-ds-base-0:1.2.11.15-97.el6_10.1.x86_64 as a component of Red Hat Enterprise Linux Server -EXTENSION(v. 6 ELS-EXTENSION); 389-ds-base-debuginfo-0:1.2.11.15-97.el6_10.1.i686 as a component of Red Hat Enterprise Linux Server -EXTENSION(v. 6 ELS-EXTENSION); 389-ds-base-debuginfo-0:1.2.11.15-97.el6_10.1.x86_64 as a component of Red Hat Enterprise Linux Server -EXTENSION(v. 6 ELS-EXTENSION); 389-ds-base-libs-0:1.2.11.15-97.el6_10.1.i686 as a component of Red Hat Enterprise Linux Server -EXTENSION(v. 6 ELS-EXTENSION); 389-ds-base-libs-0:1.2.11.15-97.el6_10.1.x86_64 as a component of Red Hat Enterprise Linux Server -EXTENSION(v. 6 ELS-EXTENSION); 389-ds-base-debuginfo-0:1.2.11.15-97.el6_10.1.i686 as a component of Red Hat Enterprise Linux Server Optional -EXTENSION (v. 6 ELS -EXTENSION); 389-ds-base-debuginfo-0:1.2.11.15-97.el6_10.1.x86_64 as a component of Red Hat Enterprise Linux Server Optional -EXTENSION (v. 6 ELS -EXTENSION); 389-ds-base-devel-0:1.2.11.15-97.el6_10.1.i686 as a component of Red Hat Enterprise Linux Server Optional -EXTENSION (v. 6 ELS -EXTENSION); 389-ds-base-devel-0:1.2.11.15-97.el6_10.1.x86_64 as a component of Red Hat Enterprise Linux Server Optional -EXTENSION (v. 6 ELS -EXTENSION); 389-ds-base-0:1.3.11.1-15.el7_9.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7 ELS); 389-ds-base-0:1.3.11.1-15.el7_9.src as a component of Red Hat Enterprise Linux Server (v. 7 ELS); 389-ds-base-0:1.3.11.1-15.el7_9.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7 ELS); 389-ds-base-debuginfo-0:1.3.11.1-15.el7_9.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7 ELS); 389-ds-base-debuginfo-0:1.3.11.1-15.el7_9.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7 ELS); 389-ds-base-libs-0:1.3.11.1-15.el7_9.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7 ELS); 389-ds-base-libs-0:1.3.11.1-15.el7_9.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7 ELS); 389-ds-base-0:1.3.11.1-15.el7_9.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); 389-ds-base-0:1.3.11.1-15.el7_9.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); 389-ds-base-0:1.3.11.1-15.el7_9.src as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); 389-ds-base-debuginfo-0:1.3.11.1-15.el7_9.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); 389-ds-base-debuginfo-0:1.3.11.1-15.el7_9.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); 389-ds-base-debuginfo-0:1.3.11.1-15.el7_9.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); 389-ds-base-debuginfo-0:1.3.11.1-15.el7_9.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); 389-ds-base-devel-0:1.3.11.1-15.el7_9.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); 389-ds-base-devel-0:1.3.11.1-15.el7_9.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); 389-ds-base-devel-0:1.3.11.1-15.el7_9.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); 389-ds-base-devel-0:1.3.11.1-15.el7_9.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); 389-ds-base-libs-0:1.3.11.1-15.el7_9.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); and 453 more
    After
    389-ds-base.src as a component of Red Hat Directory Server 12 · Fixed: 389-ds-base-0:1.2.11.15-97.el6_10.1.i686 as a component of Red Hat Enterprise Linux Server -EXTENSION(v. 6 ELS-EXTENSION); 389-ds-base-0:1.2.11.15-97.el6_10.1.src as a component of Red Hat Enterprise Linux Server -EXTENSION(v. 6 ELS-EXTENSION); 389-ds-base-0:1.2.11.15-97.el6_10.1.x86_64 as a component of Red Hat Enterprise Linux Server -EXTENSION(v. 6 ELS-EXTENSION); 389-ds-base-debuginfo-0:1.2.11.15-97.el6_10.1.i686 as a component of Red Hat Enterprise Linux Server -EXTENSION(v. 6 ELS-EXTENSION); 389-ds-base-debuginfo-0:1.2.11.15-97.el6_10.1.x86_64 as a component of Red Hat Enterprise Linux Server -EXTENSION(v. 6 ELS-EXTENSION); 389-ds-base-libs-0:1.2.11.15-97.el6_10.1.i686 as a component of Red Hat Enterprise Linux Server -EXTENSION(v. 6 ELS-EXTENSION); 389-ds-base-libs-0:1.2.11.15-97.el6_10.1.x86_64 as a component of Red Hat Enterprise Linux Server -EXTENSION(v. 6 ELS-EXTENSION); 389-ds-base-debuginfo-0:1.2.11.15-97.el6_10.1.i686 as a component of Red Hat Enterprise Linux Server Optional -EXTENSION (v. 6 ELS -EXTENSION); 389-ds-base-debuginfo-0:1.2.11.15-97.el6_10.1.x86_64 as a component of Red Hat Enterprise Linux Server Optional -EXTENSION (v. 6 ELS -EXTENSION); 389-ds-base-devel-0:1.2.11.15-97.el6_10.1.i686 as a component of Red Hat Enterprise Linux Server Optional -EXTENSION (v. 6 ELS -EXTENSION); 389-ds-base-devel-0:1.2.11.15-97.el6_10.1.x86_64 as a component of Red Hat Enterprise Linux Server Optional -EXTENSION (v. 6 ELS -EXTENSION); 389-ds-base-0:1.3.11.1-15.el7_9.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7 ELS); 389-ds-base-0:1.3.11.1-15.el7_9.src as a component of Red Hat Enterprise Linux Server (v. 7 ELS); 389-ds-base-0:1.3.11.1-15.el7_9.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7 ELS); 389-ds-base-debuginfo-0:1.3.11.1-15.el7_9.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7 ELS); 389-ds-base-debuginfo-0:1.3.11.1-15.el7_9.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7 ELS); 389-ds-base-libs-0:1.3.11.1-15.el7_9.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7 ELS); 389-ds-base-libs-0:1.3.11.1-15.el7_9.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7 ELS); 389-ds-base-0:1.3.11.1-15.el7_9.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); 389-ds-base-0:1.3.11.1-15.el7_9.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); 389-ds-base-0:1.3.11.1-15.el7_9.src as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); 389-ds-base-debuginfo-0:1.3.11.1-15.el7_9.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); 389-ds-base-debuginfo-0:1.3.11.1-15.el7_9.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); 389-ds-base-debuginfo-0:1.3.11.1-15.el7_9.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); 389-ds-base-debuginfo-0:1.3.11.1-15.el7_9.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); 389-ds-base-devel-0:1.3.11.1-15.el7_9.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); 389-ds-base-devel-0:1.3.11.1-15.el7_9.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); 389-ds-base-devel-0:1.3.11.1-15.el7_9.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); 389-ds-base-devel-0:1.3.11.1-15.el7_9.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); 389-ds-base-libs-0:1.3.11.1-15.el7_9.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); and 466 more
    Red Hat Product Security ↗
  5. BlackTree coverageBlackTree article coverage changed from no BlackTree article to 1 BlackTree article.
    Before
    no BlackTree article
    After
    1 BlackTree article
    BlackTree editorial ↗
  6. ENISA EUVD mappingEUVD-2026-72457 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2026-72457"}
    ENISA EUVD ↗
  7. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-72457↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference · Red Hat RHSA-2026:64771↗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-2026-18922 · cve.blacktree.nl