How severe is CVE-2024-41122?

CVE-2024-41122 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2024-41122?

CVE-2024-41122 affects the following packages: go.woodpecker-ci.org/woodpecker/v2 (Go), go.woodpecker-ci.org/woodpecker (Go). Ecosystems affected: Go.

How do I fix CVE-2024-41122?

Update go.woodpecker-ci.org/woodpecker/v2 to 2.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-41122 is resolved across your whole dependency graph.

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

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

How do I mitigate CVE-2024-41122 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.

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

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

CVE-2024-41122 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 50th 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 CVE-2024-41122?

CVE-2024-41122 is classified as CWE-74 (CWE-74). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2024-41122 was published on July 19, 2024 and was last updated on October 28, 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

HIGH severity

CVE-2024-41122 — woodpecker

HIGHFix: woodpecker-ci/woodpecker#3909

CVE-2024-41122 is a high-severity (CVSS 7.5) CWE-74 vulnerability in go.woodpecker-ci.org/woodpecker/v2. A fix is available for go.woodpecker-ci.org/woodpecker/v2 — see the affected versions and patch details below.

Custom environment variables allow to alter execution flow of plugins in Woodpecker

Also known asGHSA-3wf2-2pq4-4rvcGO-2024-2998

Published

Jul 19, 2024

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
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-41122.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs50th percentile — riskier than 50% of all scored CVEsHighest risk

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

2 pkgs affected

🐹go.woodpecker-ci.org/woodpecker/v2🐹go.woodpecker-ci.org/woodpecker

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

Impact

The server allow to create any user who can trigger a pipeline run malicious workflows:

Those workflows can either lead to a host takeover that runs the agent executing the workflow.
Or allow to extract the secrets who would be normally provided to the plugins who's entrypoint are overwritten.

Patches

https://github.com/woodpecker-ci/woodpecker/pull/3909 https://github.com/woodpecker-ci/woodpecker/pull/3934

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading? Enable the "gated" repo feature and review each change upfront of running

References

https://github.com/woodpecker-ci/woodpecker/pull/3909
https://github.com/woodpecker-ci/woodpecker/pull/3934
https://github.com/woodpecker-ci/woodpecker-security/issues/10 (info will be published later at https://github.com/woodpecker-ci/woodpecker/issues/3929)
https://github.com/woodpecker-ci/woodpecker/issues/3929 (info will be published later once we got adoption of the update)

Credits

Daniel Kilimnik @D_K_Dev (Neodyme AG)
Felipe Custodio Romero @localo (Neodyme AG)

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`go.woodpecker-ci.org/woodpecker/v2`	all versions	2.7.0`go get go.woodpecker-ci.org/woodpecker/v2@v2.7.0`
🐹Go	`go.woodpecker-ci.org/woodpecker`	all versions	2.7.0`go get go.woodpecker-ci.org/woodpecker@v2.7.0`

Affected Products

1 product · 1 configurations

Application

woodpeckerwoodpecker-ci

< 2.7.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for go.woodpecker-ci.org/woodpecker/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update go.woodpecker-ci.org/woodpecker/v2 to 2.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-41122 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

### Impact The server allow to create any user who can trigger a pipeline run malicious workflows: - Those workflows can either lead to a host takeover that runs the agent executing the workflow. - Or allow to extract the secrets who would be normally provided to the plugins who's entrypoint are overwritten. ### Patches https://github.com/woodpecker-ci/woodpecker/pull/3909 https://github.com/woodpecker-ci/woodpecker/pull/3934 ### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ **Enable the "gated" repo feature and review each change upfront of