p PatchFirst

CVE-2026-18651

CVE-2026-18651 · 389-ds-base: 389-ds-base: sasl plain bind installs connection credentials before account-lock check, allowing continued access as a locked account

This page contains facts from public vulnerability sources. Check the original advisory before updating.

A flaw was found in 389 Directory Server. During SASL PLAIN authentication, the server installs connection-level bind credentials before performing the account-lock check. If the account is subsequently found to be locked, the bind is reported as failed to the client, but the already-installed authenticated state on the connection is not reverted. A client that supplies valid credentials for an account that has been administratively locked can continue to use the same connection with that account's privileges, defeating account lock as an access-revocation control.

CVSS 5.4 · Medium · EPSS 0.3%

Published
Updated

Stack: system

Affected products and versions

  • red hat directory server 11

    No fix published

  • red hat directory server 12

    No fix published

  • red hat directory server 13

    No fix published

  • red hat enterprise linux 10

    No fix published

  • red hat enterprise linux 6

    No fix published

  • red hat enterprise linux 7

    No fix published

  • red hat enterprise linux 8

    No fix published

  • red hat enterprise linux 9

    No fix published

  • 389-ds-base Debian:12

    Versions
    • 2.3.1+dfsg1-1
    • 2.3.1+dfsg1-1+deb12u1
    • 2.3.4+dfsg1-1
    • 2.3.4+dfsg1-1.1
    • 2.4.4+dfsg1-1
    • 2.4.4+dfsg1-3
    • 2.4.5+dfsg1-1
    • 3.0.2+dfsg1-1
    • 3.1.1+dfsg1-1
    • 3.1.1+dfsg1-2
    • 3.1.1+dfsg1-3
    • 3.1.2+dfsg1-1
    • 3.1.2+vendor1-1
    • 3.1.2+vendor1-2
    • 3.3.0-1
    • 3.3.0-2
    • 3.3.1-1
    • 3.3.1-3
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • 389-ds-base Debian:13

    Versions
    • 3.1.2+dfsg1-1
    • 3.1.2+dfsg1-1+deb13u1
    • 3.1.2+vendor1-1
    • 3.1.2+vendor1-2
    • 3.3.0-1
    • 3.3.0-2
    • 3.3.1-1
    • 3.3.1-3
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • 389-ds-base Ubuntu:Pro:16.04:LTS

    Versions
    • 1.3.3.12-1build1
    • 1.3.3.13-1
    • 1.3.4.5-2
    • 1.3.4.8-1
    • 1.3.4.8-3
    • 1.3.4.8-3ubuntu1
    • 1.3.4.8-4
    • 1.3.4.9-1
    • 1.3.4.9-1ubuntu0.1~esm1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • 389-ds-base Ubuntu:Pro:18.04:LTS

    Versions
    • 1.3.7.5-1
    • 1.3.7.5-1build1
    • 1.3.7.5-1build2
    • 1.3.7.9-1
    • 1.3.7.10-1
    • 1.3.7.10-1ubuntu1
    • 1.3.7.10-1ubuntu1+esm1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • 389-ds-base Ubuntu:Pro:20.04:LTS

    Versions
    • 1.4.1.6-4
    • 1.4.1.6-4build1
    • 1.4.2.4-1
    • 1.4.2.4-1build1
    • 1.4.3.2-1
    • 1.4.3.2-1build1
    • 1.4.3.6-2
    • 1.4.3.6-2ubuntu0.1~esm1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • 389-ds-base Ubuntu:22.04:LTS

    Versions
    • 1.4.4.11-2build1
    • 1.4.4.11-2build2
    • 1.4.4.17-1
    • 2.0.11-2
    • 2.0.14-1
    • 2.0.15-1
    • 2.0.15-1ubuntu2
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • 389-ds-base Ubuntu:24.04:LTS

    Versions
    • 2.3.4+dfsg1-1
    • 2.4.4+dfsg1-1ubuntu1
    • 2.4.4+dfsg1-1ubuntu4
    • 2.4.4+dfsg1-3
    • 2.4.5+dfsg1-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • 389-ds-base Ubuntu:26.10

    Versions
    • 3.1.2+vendor1-2
    • 3.1.2+vendor1-2build1
    • 3.3.1-3
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • 389-ds-base Ubuntu:26.04:LTS

    Versions
    • 3.1.2+dfsg1-1
    • 3.1.2+vendor1-2
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

Original sources

Check your server →