GHSA-rgqc-3x5p-6gwg json
postgres-protocol: Panic decoding a malformed `hstore` value allows denial of service
published 5mo ago modified 2mo ago also RUSTSEC-2026-0180
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
A malicious or compromised server can return a binary `hstore` value with an invalid internal length field, causing the client to panic while decoding it.
Applications that connect only to a trusted database are not exposed; the risk applies to clients that may connect to untrusted or user-supplied servers, or whose connection can be intercepted by a man-in-the-middle.
Patch / fix
- crates.io postgres-protocol 0.6.12
Is GHSA-rgqc-3x5p-6gwg in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | postgres-protocol | <0.6.12 >=0.0.0-0, <0.6.12 |
0.6.12 |
Classification
References
-
github.com
/rust-postgres/rust-postgres/commit/a7cf84b5c46431cbca9d8ff50508c23f446efa7d
web
-
github.com
/rust-postgres/rust-postgres
package
-
github.com
/rust-postgres/rust-postgres/releases/tag/postgres-protocol-v0.6.12
web
-
rustsec.org
/advisories/RUSTSEC-2026-0180.html
web, advisory
-
crates.io
/crates/postgres-protocol
package
Sources
- GitHub Advisory GHSA-rgqc-3x5p-6gwg
- OSV RUSTSEC-2026-0180
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.