Intermittent HTTP policy bypassGHSA-68mj-9pjq-mc85
HIGHGHSA-68mj-9pjq-mc85 is a high-severity (CVSS 7.2) CWE-693 vulnerability in github.com/cilium/cilium. A fix is available for github.com/cilium/cilium — see the affected versions and patch details below.
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-68mj-9pjq-mc85.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/cilium/cilium🐹github.com/cilium/cilium🐹github.com/cilium/ciliumReal-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
Impact
Cilium's HTTP policies are not consistently applied to all traffic in the scope of the policies, leading to HTTP traffic being incorrectly and intermittently forwarded when it should be dropped.
Patches
This issue affects:
- Cilium v1.13 between v1.13.9 and v1.13.12 inclusive
- Cilium v1.14 between v1.14.0 and v1.14.7 inclusive
- Cilium v1.15.0 and v1.15.1
This issue has been patched in:
- Cilium v1.15.2
- Cilium v1.14.8
- Cilium v1.13.13
Workarounds
There is no workaround for this issue – affected users are strongly encouraged to upgrade.
Acknowledgements
The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to @romikps for discovering and reporting this issue, and @sayboras and @jrajahalme for preparing the fix.
For more information
If you have any questions or comments about this advisory, please reach out on Slack.
If you think you have found a vulnerability affecting Cilium, we strongly encourage you to report it to our security mailing list at [email protected]. This is a private mailing list for the Cilium internal security team, and your report will be treated as top priority.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/cilium/cilium | ≥ 1.13.9&&< 1.13.13 | 1.13.13go get github.com/cilium/cilium@v1.13.13 |
| 🐹Go | github.com/cilium/cilium | ≥ 1.14.0&&< 1.14.8 | 1.14.8go get github.com/cilium/cilium@v1.14.8 |
| 🐹Go | github.com/cilium/cilium | ≥ 1.15.0&&< 1.15.2 | 1.15.2go get github.com/cilium/cilium@v1.15.2 |
Affected Products
ciliumciliumDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/cilium/cilium, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/cilium/cilium to 1.13.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-68mj-9pjq-mc85 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.
Frequently Asked Questions
Is GHSA-68mj-9pjq-mc85 in your dependencies?
Find it across Go, including transitive dependencies.