How severe is GHSA-655h-hg88-5qmf?

No CVSS score has been assigned to GHSA-655h-hg88-5qmf yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-655h-hg88-5qmf?

GHSA-655h-hg88-5qmf affects the following packages: xcb (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-655h-hg88-5qmf?

Update xcb to 1.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-655h-hg88-5qmf is resolved across your whole dependency graph.

How do I detect GHSA-655h-hg88-5qmf in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for xcb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-655h-hg88-5qmf if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-655h-hg88-5qmf?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-655h-hg88-5qmf can be triaged on real exposure rather than presence alone.

Is GHSA-655h-hg88-5qmf actively exploited in the wild?

No public exploit code has been indexed for GHSA-655h-hg88-5qmf yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-655h-hg88-5qmf published, and has it been updated?

GHSA-655h-hg88-5qmf was published on August 22, 2025 and was last updated on October 28, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

GHSA-655h-hg88-5qmf — xcb

Fix: rust-x-bindings/rust-xcb#283

GHSA-655h-hg88-5qmf is a security vulnerability in xcb. A fix is available for xcb — see the affected versions and patch details below.

Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety

Also known asRUSTSEC-2025-0051

Published

Aug 22, 2025

Updated

Oct 28, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 28, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀xcb

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

The API of xcb::Connection has constructors which allow an arbitrary RawFd to be used as a socket connection. On either failure of these constructors or on the drop of Connection, it closes the associated file descriptor. Thus, a program which uses an OwnedFd (such as a UnixStream) as the file descriptor can close the file descriptor and continue to attempt using it or close an already-closed file descriptor, violating I/O safety.

Starting in version 1.6.0, xcb provides Connection::connect_with_fd and Connection::connect_with_fd_and_extensions as safe alternatives and deprecates the problematic functions.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`xcb`	all versions	1.6.0`cargo update -p xcb --precise 1.6.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for xcb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update xcb to 1.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-655h-hg88-5qmf is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-655h-hg88-5qmf can be triaged on real exposure rather than presence alone.

Tailored to GHSA-655h-hg88-5qmf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The API of `xcb::Connection` has constructors which allow an arbitrary `RawFd` to be used as a socket connection. On either failure of these constructors or on the drop of `Connection`, it closes the associated file descriptor. Thus, a program which uses an `OwnedFd` (such as a `UnixStream`) as the file descriptor can close the file descriptor and continue to attempt using it or close an already-closed file descriptor, violating I/O safety. Starting in version 1.6.0, `xcb` provides `Connection::connect_with_fd` and `Connection::connect_with_fd_and_extensions` as safe alternatives and deprecat

O3 Security · Impact-Aware SCA

Is GHSA-655h-hg88-5qmf in your dependencies?

O3 Security finds GHSA-655h-hg88-5qmf across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works