How severe is GHSA-2jx2-qcm4-rf9h?

No CVSS score has been assigned to GHSA-2jx2-qcm4-rf9h yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2jx2-qcm4-rf9h?

GHSA-2jx2-qcm4-rf9h affects the following packages: github.com/grpc/grpc-swift (SwiftURL). Ecosystems affected: SwiftURL.

How do I fix GHSA-2jx2-qcm4-rf9h?

Update github.com/grpc/grpc-swift to 1.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2jx2-qcm4-rf9h is resolved across your whole dependency graph.

How do I detect GHSA-2jx2-qcm4-rf9h in my SwiftURL dependencies?

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

How do I mitigate GHSA-2jx2-qcm4-rf9h if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-2jx2-qcm4-rf9h actively exploited in the wild?

No public exploit code has been indexed for GHSA-2jx2-qcm4-rf9h 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.

What is the EPSS score for GHSA-2jx2-qcm4-rf9h?

GHSA-2jx2-qcm4-rf9h has an EPSS (Exploit Prediction Scoring System) score of 2.1%, placing it in the 82th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-2jx2-qcm4-rf9h published, and has it been updated?

GHSA-2jx2-qcm4-rf9h was published on June 9, 2023 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 SwiftURL

Not in CISA KEV

Incomplete Internal State Distinction in GRPCWebToHTTP2ServerCodecGHSA-2jx2-qcm4-rf9h

GHSA-2jx2-qcm4-rf9h is a security vulnerability in github.com/grpc/grpc-swift. A fix is available for github.com/grpc/grpc-swift — see the affected versions and patch details below.

Also known asCVE-2021-36153

Published

Jun 9, 2023

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs82th percentile — riskier than 82% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

📦github.com/grpc/grpc-swift

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

Description

Impact

Affected gRPC Swift servers are vulnerable to precondition failures when parsing certain gRPC Web requests. This may lead to a denial of service.

Patches

The problem has been fixed in 1.2.0.

Workarounds

No workaround is available. Users must upgrade.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦SwiftURL	`github.com/grpc/grpc-swift`	all versions	1.2.0

Affected Products

1 product · 2 configurations

Application

grpc swiftlinuxfoundation

2 versions

1.1.01.1.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/grpc/grpc-swift, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/grpc/grpc-swift to 1.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2jx2-qcm4-rf9h is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

### Impact Affected gRPC Swift servers are vulnerable to precondition failures when parsing certain gRPC Web requests. This may lead to a denial of service. ### Patches The problem has been fixed in 1.2.0. ### Workarounds No workaround is available. Users must upgrade.

O3 Security · Impact-Aware SCA

Is GHSA-2jx2-qcm4-rf9h in your dependencies?

Find it across SwiftURL, including transitive dependencies.

Scan my dependencies How O3 SCA works

Incomplete Internal State Distinction in GRPCWebToHTTP2ServerCodecGHSA-2jx2-qcm4-rf9h

EPSS Exploitation Probability

Real-World Exposure

Description

Impact

Patches

Workarounds

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-2jx2-qcm4-rf9h in your dependencies?