How severe is GHSA-p2gr-hm8g-q772?

No CVSS score has been assigned to GHSA-p2gr-hm8g-q772 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-p2gr-hm8g-q772?

GHSA-p2gr-hm8g-q772 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-p2gr-hm8g-q772?

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

How do I detect GHSA-p2gr-hm8g-q772 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-p2gr-hm8g-q772 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-p2gr-hm8g-q772?

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

Is GHSA-p2gr-hm8g-q772 actively exploited in the wild?

No public exploit code has been indexed for GHSA-p2gr-hm8g-q772 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-p2gr-hm8g-q772?

GHSA-p2gr-hm8g-q772 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 35th 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-p2gr-hm8g-q772?

GHSA-p2gr-hm8g-q772 is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-p2gr-hm8g-q772 published, and has it been updated?

GHSA-p2gr-hm8g-q772 was published on December 30, 2025 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-p2gr-hm8g-q772: server

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
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-p2gr-hm8g-q772.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs35th percentile — riskier than 35% 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

When frontend.enableExecuteMultiOperation is enabled, the server can apply namespace-scoped validation and feature gates for the embedded StartWorkflowExecutionRequest using its Namespace field rather than the outer, authorized ExecuteMultiOperationRequest.Namespace. This allows a caller authorized for one namespace to bypass that namespace's limits/policies by setting the embedded start request's namespace to a different namespace. The workflow is still created in the outer (authorized) namespace; only validation/gating is performed under the wrong namespace context. This issue affects Temporal: from 1.24.0 through 1.29.1. Fixed in 1.27.4, 1.28.2, 1.29.2.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`go.temporal.io/server`	≥ 1.24.0&&< 1.27.4	1.27.4`go get go.temporal.io/server@v1.27.4`
🐹Go	`go.temporal.io/server`	≥ 1.28.0&&< 1.28.2	1.28.2`go get go.temporal.io/server@v1.28.2`
🐹Go	`go.temporal.io/server`	≥ 1.29.0&&< 1.29.2	1.29.2`go get go.temporal.io/server@v1.29.2`

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.27.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p2gr-hm8g-q772 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-p2gr-hm8g-q772 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-p2gr-hm8g-q772. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

When frontend.enableExecuteMultiOperation is enabled, the server can apply namespace-scoped validation and feature gates for the embedded StartWorkflowExecutionRequest using its Namespace field rather than the outer, authorized ExecuteMultiOperationRequest.Namespace. This allows a caller authorized for one namespace to bypass that namespace's limits/policies by setting the embedded start request's namespace to a different namespace. The workflow is still created in the outer (authorized) namespace; only validation/gating is performed under the wrong namespace context. This issue affects Tempor

O3 Security · Impact-Aware SCA

Is GHSA-p2gr-hm8g-q772 in your dependencies?

O3 Security finds GHSA-p2gr-hm8g-q772 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-p2gr-hm8g-q772 — server