How severe is GHSA-fgm3-q9r5-43v9?

No CVSS score has been assigned to GHSA-fgm3-q9r5-43v9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-fgm3-q9r5-43v9?

GHSA-fgm3-q9r5-43v9 affects the following packages: github.com/ctfer-io/romeo/environment/deploy (Go). Ecosystems affected: Go.

How do I fix GHSA-fgm3-q9r5-43v9?

Update github.com/ctfer-io/romeo/environment/deploy to 0.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fgm3-q9r5-43v9 is resolved across your whole dependency graph.

How do I detect GHSA-fgm3-q9r5-43v9 in my Go dependencies?

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

How do I mitigate GHSA-fgm3-q9r5-43v9 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-fgm3-q9r5-43v9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-fgm3-q9r5-43v9 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-fgm3-q9r5-43v9?

GHSA-fgm3-q9r5-43v9 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-fgm3-q9r5-43v9?

GHSA-fgm3-q9r5-43v9 is classified as CWE-284 (CWE-284). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-fgm3-q9r5-43v9 published, and has it been updated?

GHSA-fgm3-q9r5-43v9 was published on March 16, 2026 and was last updated on March 26, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

Romeo's invalid NetworkPolicy enables a malicious actor to pivot into another namespaceGHSA-fgm3-q9r5-43v9

Fix: ctfer-io/romeo@3bb5e9d

GHSA-fgm3-q9r5-43v9 is a CWE-284 vulnerability in github.com/ctfer-io/romeo/environment/deploy. A fix is available for github.com/ctfer-io/romeo/environment/deploy — see the affected versions and patch details below.

Also known asCVE-2026-32737GO-2026-4714

Published

Mar 16, 2026

Updated

Mar 26, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

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-fgm3-q9r5-43v9.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk+0.01%

Lower risk than most CVEs35th percentile — riskier than 35% 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/ctfer-io/romeo/environment/deploy

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

Romeo gives the capability to reach high code coverage of Go ≥1.20 apps by helping to measure code coverage for functional and integration tests within GitHub Actions. Prior to version 0.2.1, due to a mis-written NetworkPolicy, a malicious actor can pivot from the "hardened" namespace to any Pod out of it. This breaks the security-by-default property expected as part of the deployment program, leading to a potential lateral movement. Removing the inter-ns NetworkPolicy patches the vulnerability in version 0.2.1. If updates are not possible in production environments, manually delete inter-ns and update as soon as possible. Given one's context, delete the failing network policy that should be prefixed by inter-ns- in the target namespace.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/ctfer-io/romeo/environment/deploy`	all versions	0.2.1`go get github.com/ctfer-io/romeo/environment/deploy@v0.2.1`

Affected Products

1 product · 1 configurations

Application

romeoctfer-io

< 0.2.1

range

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/ctfer-io/romeo/environment/deploy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/ctfer-io/romeo/environment/deploy to 0.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fgm3-q9r5-43v9 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Impact Due to a mis-written NetworkPolicy, a malicious actor can pivot from the "hardened" namespace to any Pod out of it. This breaks the security-by-default property expected as part of the deployment program, leading to a potential lateral movement. ### Patch Removing the `inter-ns` NetworkPolicy patches the vulnerability. If updates are not possible in production environments, we recommend to manually delete it and update as soon as possible. ### Workaround Given your context, delete the failing network policy that should be prefixed by `inter-ns-` in the target namespace.

O3 Security · Impact-Aware SCA

Is GHSA-fgm3-q9r5-43v9 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works