graphprotocol / graphprotocol/graph-node

RUSTSEC-2026-0180: Panic decoding a malformed `hstore` value allows denial of service

Open
#6,624 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
3.2k
Forks
1.1k
Avg merge
4d 1h
Merged PRs (30d)
1

Description

Panic decoding a malformed hstore value allows denial of service

Details
Package postgres-protocol
Version 0.6.9
URL https://github.com/rust-postgres/rust-postgres/commit/a7cf84b5c46431cbca9d8ff50508c23f446efa7d
Date 2026-06-12
Patched versions >=0.6.12

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.

See advisory page for additional details.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file, test, or entry point is named. Start by reading the linked RUSTSEC-2026-0180 advisory and inspecting how graph-node resolves the postgres-protocol dependency; done means confirming the affected package is no longer resolved below 0.6.12 and validating the relevant database connection path.

Written by the indexing model from the issue text.

Assessment

Tech stack
postgres, rust
Domain
backend, databases, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.