CVE-2026-39946

OpenBao allows SQL Injection in PostgreSQL database secrets engine

CVSS 4.0 4.6 MEDIUMEUVD CVSS 4.0 4.6 CVSS 4.0 · [email protected] · Secondary 4.6 MEDIUMCVSS 3.1 · [email protected] · Primary 4.9 MEDIUMCVSS_V3 CVSS_V4 Publisher rating MODERATEFixed by github.com/openbao/openbao 0.0.0-20260420155735-b596b0882620osv · severity unknownFixed by github.com/openbao/openbao 0.0.0-20260420155735-b596b0882620KEV status unknown

Original advisory

cve-program · CVE-2026-39946

Published

OpenBao is an open source identity-based secrets management system. Prior to version 2.5.3, when OpenBao revoked privileges on a role in the PostgreSQL database secrets engine, OpenBao failed to use proper database quoting on schema names provided by PostgreSQL. This could lead to role revocation failures, or more rarely, SQL injection as the management user. This vulnerability was original from HashiCorp Vault. The vulnerability is addressed in v2.5.3. As a workaround, audit table schemas and ensure database users cannot create new schemas and grant privileges on them.

Read the publisher's advisory

euvd · EUVD-2026-24035

Published

Read the publisher's advisory

nvd · CVE-2026-39946

Published

Read the publisher's advisory

osv · GHSA-6vgr-cp5c-ffx3

Published

### Impact When OpenBao revoked privileges on a role in the PostgreSQL database secrets engine, OpenBao failed to use proper database quoting on schema names provided by PostgreSQL. This could lead to role revocation failures, or more rarely, SQL injection as the management user. This vulnerability was originally from HashiCorp Vault. ### Patches This was addressed in v2.5.3. ### Workarounds Audit table schemas and ensure database users cannot create new schemas and grant privileges on them.

Read the publisher's advisory

osv · GO-2026-5192

Published

OpenBao's SQL Injection in PostgreSQL database secrets engine in github.com/openbao/openbao

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

Risk history

Compare earlier KEV listings and EPSS scores. Advisory wording and affected versions have a separate history.

When does an EPSS score appear as a change?

A prediction change is reported when EPSS rises from below 10% to 10% or higher. Every daily score change from the last 30 days stays in this history. Before that, it keeps KEV changes and moves between EPSS bands (0.1%, 1%, 5%, 10%, 20%, 50% and 90%).

Advisory history

15 saved versions

See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.

How advisory history works

Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.

15 Nov 2026 21:53:05 UTC