How severe is CVE-2026-1966?

CVE-2026-1966 has a CVSS 4.0 base score of 2.4, rated low severity.

Is CVE-2026-1966 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (6th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-1966?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2026-1966 have an EU (EUVD) identifier?

Yes. CVE-2026-1966 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-5553.

When was CVE-2026-1966 published?

CVE-2026-1966 was published on 2026-02-05 and last updated on 2026-06-17.

CVE-2026-1966

CVE-2026-1966 is a low-severity vulnerability with a CVSS 4.0 base score of 2.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-522.

Key facts

Severity: Low (CVSS 4.0 base score 2.4)
EPSS exploit prediction: 0% (6th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-5553
Weakness: CWE-522
Published: 2026-02-05
Last modified: 2026-06-17

Description

YugabyteDB Anywhere displays LDAP bind passwords configured via gflags in cleartext within the web UI. An authenticated user with access to the configuration view could obtain LDAP credentials, potentially enabling unauthorized access to external directory services.

Frequently asked questions

What is CVE-2026-1966?: YugabyteDB Anywhere displays LDAP bind passwords configured via gflags in cleartext within the web UI. An authenticated user with access to the configuration view could obtain LDAP credentials, potentially enabling unauthorized access to external directory services.
How severe is CVE-2026-1966?: CVE-2026-1966 has a CVSS 4.0 base score of 2.4, rated low severity.
Is CVE-2026-1966 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (6th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-1966?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-1966 have an EU (EUVD) identifier?: Yes. CVE-2026-1966 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-5553.
When was CVE-2026-1966 published?: CVE-2026-1966 was published on 2026-02-05 and last updated on 2026-06-17.

References

https://docs.yugabyte.com/stable/secure/vulnerability-disclosure-policy/

Other CWE-522 (Insufficiently Protected Credentials) vulnerabilities

CVE-2026-7312 — Critical (CVSS 10.0): CWE‑522: Insufficiently Protected Credentials in web services in Progress Sitefinity version from 14.0.7700 to…
CVE-2026-29128 — Critical (CVSS 10.0): IDC SFX2100 Satellite Receiver firmware ships with multiple daemon configuration files for routing components (e.g.,…
CVE-2025-54863 — Critical (CVSS 10.0): Radiometrics VizAir is vulnerable to exposure of the system's REST API key through a publicly accessible configuration…
CVE-2024-12799 — Critical (CVSS 10.0): Insufficiently Protected Credentials vulnerability in OpenText Identity Manager Advanced Edition on Windows, Linux, 64…
CVE-2024-51545 — Critical (CVSS 10.0): Username Enumeration vulnerabilities allow access to application level username add, delete, modify and list…
CVE-2023-1778 — Critical (CVSS 10.0): This vulnerability exists in GajShield Data Security Firewall firmware versions prior to v4.28 (except v4.21) due to…

Browse all CWE-522 (Insufficiently Protected Credentials) vulnerabilities →