Jenkins · Code execution
Jenkins Remote Code Execution Vulnerability
At a glance
Actively exploited in the wild — prioritise confirming exposure.
Medium rather than High: exposure is scored at a default because we cannot see your systems or suppliers. If you run or depend on Jenkins, treat it as High.
Briefing
There is no written leader briefing for this story yet. These questions come from the facts we hold.
Questions to ask IT
- Do we run Jenkins, and which versions?
- Is any of it reachable from the internet?
- Have we checked whether it has already been used against us?
- If it is not yet patched, what mitigation is in place, and will the fix be done by 11 Nov?
Next steps
- Confirm exposure, mitigation status and any service interruption risk.
Vulnerability facts
Full CVE detail CVE-2017-1000353- 9.8 · CriticalExploitable over the network without any account, and no one has to click or open anything. High impact on confidentiality, integrity and availability.CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Listed: attacks using it have been seen (on the catalogue since )
- Elevated attack likelihood (~99.7% in 30 days)
- 2.56 and earlier
No technical write-up beyond these facts and the summary below yet.
Next steps
- Confirm whether affected products/versions are present and prioritise patching or mitigations
Summary
- This vulnerability that could allowed attackers to transfer a serialised Java SignedObject object to the remoting-based Jenkins CLI, that would be deserialised using a new ObjectInputStream, bypassing the existing blocklist-based protection mechanism.
- CVE-2017-1000353 is listed in known-exploited catalogue (exploitation in the wild)
- CVE-2017-1000353 has estimated attack likelihood 0.99679 (~99.7% estimated chance of exploitation in 30 days; 99.9th percentile) as of 2026-07-31 — probability signal, not confirmed exploitation
- Authoritative catalogues report active exploitation of this vulnerability.
Why this matters in the UK
- Known-exploited catalogue reports exploitation in the wild
Products and services involved
- Jenkins93% match confidence · CVE-2017-1000353
Pulse
Last checked 28m ago · Next recheck 10 Nov 2026, 03:39 UK time · 2 quiet checks collapsed
held at 99.7%; ranking metadata was updated.
Listed on the — prioritise confirming exposure and patching.
3 quiet checks hidden.
Sources
Jenkins Remote Code Execution Vulnerability
How we know
Statements extracted from sources. Higher confidence means stronger corroboration.
- ConfirmedHeadline90% confidence
Jenkins Remote Code Execution Vulnerability
- ConfirmedSummary fact75% confidence
Jenkins contains a remote code execution vulnerability. This vulnerability that could allowed attackers to transfer a serialized Java SignedObject object to the remoting-based Jenkins CLI, that would be deserialized using a new ObjectInputStream, bypassing the existing blocklist-based protection mechanism. Affects Jenkins Jenkins. Known ransomware campaign use: Unknown.
- ConfirmedCVE identifier95% confidence
Event involves CVE-2017-1000353
- ConfirmedKnown-exploited catalogue98% confidence
CVE-2017-1000353 is listed in known-exploited catalogue (exploitation in the wild)
- ConfirmedEstimated attack likelihood95% confidence
CVE-2017-1000353 has estimated attack likelihood 0.99679 (~99.7% estimated chance of exploitation in 30 days; 99.9th percentile) as of 2026-07-31 — probability signal, not confirmed exploitation

