How severe is GHSA-q98v-9f9w-f49q?

No CVSS score has been assigned to GHSA-q98v-9f9w-f49q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-q98v-9f9w-f49q?

GHSA-q98v-9f9w-f49q affects the following packages: go.temporal.io/server (Go), go.temporal.io/server (Go), go.temporal.io/server (Go). Ecosystems affected: Go.

How do I fix GHSA-q98v-9f9w-f49q?

Update go.temporal.io/server to 1.28.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q98v-9f9w-f49q is resolved across your whole dependency graph.

How do I detect GHSA-q98v-9f9w-f49q in my Go dependencies?

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

How do I mitigate GHSA-q98v-9f9w-f49q 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-q98v-9f9w-f49q?

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

Is GHSA-q98v-9f9w-f49q actively exploited in the wild?

No public exploit code has been indexed for GHSA-q98v-9f9w-f49q 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-q98v-9f9w-f49q?

GHSA-q98v-9f9w-f49q has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 44th 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.

What type of vulnerability is GHSA-q98v-9f9w-f49q?

GHSA-q98v-9f9w-f49q is classified as Missing Authentication (CWE-306). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-q98v-9f9w-f49q published, and has it been updated?

GHSA-q98v-9f9w-f49q was published on April 10, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-q98v-9f9w-f49q: server

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-q98v-9f9w-f49q.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs44th percentile — riskier than 44% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

3 pkgs affected

🐹go.temporal.io/server🐹go.temporal.io/server🐹go.temporal.io/server

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

Description

The frontend gRPC server's streaming interceptor chain did not include the authorization interceptor. When a ClaimMapper and Authorizer are configured, unary RPCs enforce authentication and authorization, but the streaming AdminService/StreamWorkflowReplicationMessages endpoint accepted requests without credentials. This endpoint is registered on the same port as WorkflowService and cannot be disabled independently. An attacker with network access to the frontend port could open the replication stream without authentication. Data exfiltration is possible, but only when a configured replication target is correctly configured and the attacker has knowledge of the cluster configuration, as the history service validates cluster IDs and peer membership before returning replication data.

The fix was applied per release line: it is present in 1.28.4, 1.29.6, 1.30.4, 1.31.2, and 1.32.0 and later releases on each line. Releases 1.31.0 and 1.31.1 do not contain the fix and are affected.

Temporal Cloud is not affected.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`go.temporal.io/server`	all versions	1.28.4`go get go.temporal.io/server@v1.28.4`
🐹Go	`go.temporal.io/server`	≥ 1.29.0-135.0&&< 1.29.6	1.29.6`go get go.temporal.io/server@v1.29.6`
🐹Go	`go.temporal.io/server`	≥ 1.30.0-143.0&&< 1.30.4	1.30.4`go get go.temporal.io/server@v1.30.4`

Detection & mitigation playbook

Open-source dependency

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

Tailored to GHSA-q98v-9f9w-f49q. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The frontend gRPC server's streaming interceptor chain did not include the authorization interceptor. When a ClaimMapper and Authorizer are configured, unary RPCs enforce authentication and authorization, but the streaming AdminService/StreamWorkflowReplicationMessages endpoint accepted requests without credentials. This endpoint is registered on the same port as WorkflowService and cannot be disabled independently. An attacker with network access to the frontend port could open the replication stream without authentication. Data exfiltration is possible, but only when a configured replicatio

O3 Security · Impact-Aware SCA

Is GHSA-q98v-9f9w-f49q in your dependencies?

O3 Security finds GHSA-q98v-9f9w-f49q across Go 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

GHSA-q98v-9f9w-f49q — server