NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

CVE-2022-34296 — skipper

HIGHFix: zalando/skipper#2028

CVE-2022-34296 is a high-severity (CVSS 7.5) vulnerability in github.com/zalando/skipper. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for github.com/zalando/skipper — see the affected versions and patch details below.

Query predicate bypass in Zalando Skipper

Also known asGHSA-qx2j-85q5-ffp8GO-2022-0494
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs67th percentile — riskier than 67% of all scored CVEsHighest risk
0.00%0.55%1.10%1.65%0.2%1.1%May 26Sep 26Nov 26

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

1 pkg affected
🐹github.com/zalando/skipper

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

In Zalando Skipper before 0.13.218, a query predicate could be bypassed via a prepared request.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/zalando/skipperall versions0.13.218go get github.com/zalando/skipper@v0.13.218

Affected Products

1 product · 1 configurations
Application
skipperzalando
< 0.13.218
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

In Zalando Skipper before 0.13.218, a query predicate could be bypassed …

github.comNVDJul 2022

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update github.com/zalando/skipper to 0.13.218 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-34296 is resolved across your whole dependency graph.

  3. 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

In Zalando Skipper before 0.13.218, a query predicate could be bypassed via a prepared request.
O3 Security · Impact-Aware SCA

Is CVE-2022-34296 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2022-34296: skipper — Fixed in 0.13.218