Bundesamt für Sicherheit in der Informationstechnik Amazon · PostgreSQL: Mehrere Schwachstellen
Affects Bundesamt für Sicherheit in der Informationstechnik AmazonSource GCVE Database
Not known to be exploited · CVSS 8.8 High · fixed in 18.6 : patch Bundesamt für Sicherheit in der Informationstechnik Amazon soon.
Data as of 19 Nov 2026, 12:18 UTC
- Patch
- Available – fixed in 18.6, 17.11, 16.15 +3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PostgreSQL | Affected
| Fixed in
|
| PostgreSQL | Affected
| Fixed in
|
| PostgreSQL | Affected
| Fixed in
|
| PostgreSQL | Affected
| Fixed in
|
| PostgreSQL | Affected
| Fixed in
|
Postgresqlpostgresql/postgresqlpkg:deb/postgresql/postgresqlOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
Multiple vulnerabilities have been identified in PostgreSQL, a widely used open-source database system. The information provided does not specify the nature, impact, or affected versions of these vulnerabilities beyond a single version label. No CVSS score or detailed technical data is available.
References
- wid.cert-bund.de/.well-known/csaf/white/2026/wid-sec-w-2026-2844.json (opens in a new tab)
- wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2026-2844 (opens in a new tab)
- postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/ (opens in a new tab)
- postgresql.org/support/security/CVE-2026-14662/ (opens in a new tab)
- postgresql.org/support/security/CVE-2026-14663/ (opens in a new tab)
- postgresql.org/support/security/CVE-2026-14664/ (opens in a new tab)
- postgresql.org/support/security/CVE-2026-14666/ (opens in a new tab)
- postgresql.org/support/security/CVE-2026-14668/ (opens in a new tab)
- postgresql.org/support/security/CVE-2026-14669/ (opens in a new tab)
- postgresql.org/support/security/CVE-2026-14670/ (opens in a new tab)
- postgresql.org/support/security/CVE-2026-14671/ (opens in a new tab)
- postgresql.org/support/security/CVE-2026-14672/ (opens in a new tab)
- postgresql.org/support/security/CVE-2026-14673/ (opens in a new tab)
- postgresql.org/support/security/CVE-2026-14676/ (opens in a new tab)
- postgresql.org/support/security/CVE-2026-14677/ (opens in a new tab)
- postgresql.org/support/security/CVE-2026-14678/ (opens in a new tab)
- postgresql.org/support/security/CVE-2026-14679/ (opens in a new tab)
- postgresql.org/support/security/CVE-2026-14680/ (opens in a new tab)
- postgresql.org/support/security/CVE-2026-14681/ (opens in a new tab)
- postgresql.org/support/security/CVE-2026-15741/ (opens in a new tab)