How severe is GHSA-g588-cjg3-6g78?

No CVSS score has been assigned to GHSA-g588-cjg3-6g78 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-g588-cjg3-6g78?

GHSA-g588-cjg3-6g78 affects the following packages: steamworks (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-g588-cjg3-6g78?

Update steamworks to 0.13.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g588-cjg3-6g78 is resolved across your whole dependency graph.

How do I detect GHSA-g588-cjg3-6g78 in my crates.io dependencies?

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

How do I mitigate GHSA-g588-cjg3-6g78 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-g588-cjg3-6g78?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-g588-cjg3-6g78 can be triaged on real exposure rather than presence alone.

Is GHSA-g588-cjg3-6g78 actively exploited in the wild?

No public exploit code has been indexed for GHSA-g588-cjg3-6g78 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-g588-cjg3-6g78 published, and has it been updated?

GHSA-g588-cjg3-6g78 was published on May 11, 2026 and was last updated on May 12, 2026. 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-g588-cjg3-6g78 — steamworks

GHSA-g588-cjg3-6g78 is a security vulnerability in steamworks. A fix is available for steamworks — see the affected versions and patch details below.

Steamworks game clients/servers using P2P authentication vulnerable to denial of service

Also known asRUSTSEC-2026-0121

Published

May 11, 2026

Updated

May 12, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of May 12, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀steamworks

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

Processing the raw ValidateAuthTicketResponse_t callback data panics when the m_eAuthSessionResponse field is k_EAuthSessionResponseAuthTicketNetworkIdentityFailure. This can lead to denial of service in game clients and servers using the begin_authentication_session API to authenticate players if a malicious game client sends an authentication ticket with a network identity that does not match that of the verifier.

Affected Packages

1 total 1 fixed

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

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for steamworks, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update steamworks to 0.13.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g588-cjg3-6g78 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-g588-cjg3-6g78 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-g588-cjg3-6g78. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Processing the raw `ValidateAuthTicketResponse_t` callback data panics when the `m_eAuthSessionResponse` field is `k_EAuthSessionResponseAuthTicketNetworkIdentityFailure`. This can lead to denial of service in game clients and servers using the `begin_authentication_session` API to authenticate players if a malicious game client sends an authentication ticket with a network identity that does not match that of the verifier.

O3 Security · Impact-Aware SCA

Is GHSA-g588-cjg3-6g78 in your dependencies?

O3 Security finds GHSA-g588-cjg3-6g78 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