CVSS 4.0
9.3 criticalCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NCritical (9.3). EPSS 0.6% estimated probability of exploitation activity in the next 30 days.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExplain CVE-2026-119923 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-119923?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-119923?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-119923 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| AWS babelfish-for-postgresql | from 1.0 through 1.5 |
| AWS babelfish-for-postgresql | from 2.1 through 2.15 |
| AWS babelfish-for-postgresql | from 3.1 through 3.12 |
| AWS babelfish-for-postgresql | from 4.0 through 4.8 |
| AWS babelfish-for-postgresql | from 5.1 through 5.4 |
| Amazon Aurora PostgreSQL with Babelfish | from 1.0.0 before 1.5.5 |
| Amazon Aurora PostgreSQL with Babelfish | from 1.6.0 before 1.17.2 |
| Amazon Aurora PostgreSQL with Babelfish | from 2.0.0 before 2.3.5 |
| Amazon Aurora PostgreSQL with Babelfish | from 2.4.0 before 2.12.4 |
| Amazon Aurora PostgreSQL with Babelfish | from 2.13.0 before 2.13.3 |
| Amazon Aurora PostgreSQL with Babelfish | from 2.14.0 before 2.14.2 |
| Amazon Aurora PostgreSQL with Babelfish | from 2.15.0 before 2.15.2 |
| Amazon Aurora PostgreSQL with Babelfish | from 2.16.0 before 2.16.1 |
| Amazon Aurora PostgreSQL with Babelfish | from 3.0.0 before 3.8.4 |
| Amazon Aurora PostgreSQL with Babelfish | from 3.9.0 before 3.9.4 |
| Amazon Aurora PostgreSQL with Babelfish | from 3.10.0 before 3.10.3 |
| Amazon Aurora PostgreSQL with Babelfish | from 3.11.0 before 3.11.2 |
| Amazon Aurora PostgreSQL with Babelfish | from 3.12.0 before 3.12.2 |
| Amazon Aurora PostgreSQL with Babelfish | from 3.13.0 before 3.13.1 |
| Amazon Aurora PostgreSQL with Babelfish | from 4.0.0 before 4.5.5 |
| Amazon Aurora PostgreSQL with Babelfish | from 4.6.0 before 4.6.3 |
| Amazon Aurora PostgreSQL with Babelfish | from 4.7.0 before 4.7.2 |
| Amazon Aurora PostgreSQL with Babelfish | from 4.8.0 before 4.8.2 |
| Amazon Aurora PostgreSQL with Babelfish | from 4.9.0 before 4.9.1 |
| Amazon Aurora PostgreSQL with Babelfish | from 5.0.0 before 5.1.4 |
| Amazon Aurora PostgreSQL with Babelfish | from 5.2.0 before 5.2.3 |
| Amazon Aurora PostgreSQL with Babelfish | from 5.3.0 before 5.3.2 |
| Amazon Aurora PostgreSQL with Babelfish | from 5.4.0 before 5.4.2 |
| Amazon Aurora PostgreSQL with Babelfish | 5.5.0 |
| Amazon Aurora PostgreSQL with Babelfish | from 6.0.0 before 6.0.2 |
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.