How severe is CVE-2024-6535?

CVE-2024-6535 has a CVSS score of 5.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2024-6535?

CVE-2024-6535 affects the following packages: github.com/skupperproject/skupper (Go). Ecosystems affected: Go.

How do I fix CVE-2024-6535?

Update github.com/skupperproject/skupper to 0.0.0-20240703184342-c26bce4079ff or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-6535 is resolved across your whole dependency graph.

How do I detect CVE-2024-6535 in my Go dependencies?

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

How do I mitigate CVE-2024-6535 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 CVE-2024-6535?

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

Is CVE-2024-6535 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-6535 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 CVE-2024-6535?

CVE-2024-6535 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 43th 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.

When was CVE-2024-6535 published, and has it been updated?

CVE-2024-6535 was published on July 17, 2024 and was last updated on November 18, 2024. 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

MEDIUM severity

CVE-2024-6535 — skupper

MEDIUMFix: skupperproject/skupper@d2cb378

CVE-2024-6535 is a medium-severity (CVSS 5.9) vulnerability in github.com/skupperproject/skupper. A fix is available for github.com/skupperproject/skupper — see the affected versions and patch details below.

Skupper uses a static cookie secret for the openshift oauth-proxy

Also known asGO-2024-2987

Published

Jul 17, 2024

Updated

Nov 18, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 21, 2026 · OSV.dev, 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 CVE-2024-6535.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs43th percentile — riskier than 43% 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.

How urgent is this, really

CVE-2024-6535 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

1 pkg affected

🐹github.com/skupperproject/skupper

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

A flaw was found in Skupper. When Skupper is initialized with the console-enabled and with console-auth set to Openshift, it configures the openshift oauth-proxy with a static cookie-secret. In certain circumstances, this may allow an attacker to bypass authentication to the Skupper console via a specially-crafted cookie.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/skupperproject/skupper`	all versions	0.0.0-20240703184342-c26bce4079ff`go get github.com/skupperproject/skupper@v0.0.0-20240703184342-c26bce4079ff`

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/skupperproject/skupper, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/skupperproject/skupper to 0.0.0-20240703184342-c26bce4079ff or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-6535 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 CVE-2024-6535 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2024-6535. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Service Interconnect 1.4 for RHEL 9	`service-interconnect/skupper-flow-collector-rhel9:1.4.7-1`	RHSA-2024:4865
Service Interconnect 1 for RHEL 9	`service-interconnect/skupper-flow-collector-rhel9:1.5.5-1`	RHSA-2024:4871

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2024-6535 in your dependencies?

O3 Security finds CVE-2024-6535 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