Jenkins, the automation server that builds and ships code for a very large share of the software industry, has patched five security issues in its latest weekly and long term support releases. One of them is rated critical, and it undoes a protection the project built specifically to stop a class of attack that has plagued Java applications for a decade.
CVE-2026-70426 carries a CVSS base score of 9.0. The flaw sits in Remoting, the component Jenkins uses to talk to its build agents. Jenkins normally runs incoming serialized data through a class filter known as JEP-200, an allowlist that decides which Java classes are safe to rebuild from untrusted input. That check is the project's main defense against deserialization attacks, where an attacker sends a crafted object that does something dangerous while it is being unpacked. According to the advisory, the JEP-200 filter is not applied to classes resolved through a fallback path in Remoting's deserialization implementation, so the filter can be bypassed for any class already on the Jenkins core classpath.
Who can trigger it matters as much as the score. The advisory says the bypass is available to agent processes, to code running on agents, and to any account holding the Agent/Connect permission. That makes it a trust boundary problem at exactly the point where the Jenkins controller accepts data from its own agents, and agents are the least trusted part of most Jenkins estates, frequently running pull request code submitted from outside the organization. Jenkins has not published an exploitation path, and none has been reported publicly.
What's affected
Jenkins weekly 2.575 and earlier, and Jenkins LTS 2.568.1 and earlier. In Remoting terms the affected builds are 3384.v60d89463d9e0 and earlier, with the exception of 3355.3357.v931d3c992987. The same advisory covers four further issues, CVE-2026-70427 through CVE-2026-70430. HKCERT, Hong Kong's national CERT, lists the impacts of the release collectively as spoofing, security restriction bypass, remote code execution, data manipulation and elevation of privilege, and rates the bundle medium risk. No individual scores had been published for those other four at the time of writing, so treat the critical rating as belonging to CVE-2026-70426 alone until the rest are scored.
What you should do
Upgrade. Fixed versions ship alongside the Jenkins security advisory of 5 August 2026, which is the authoritative list of affected components and releases. Until you can, audit who holds the Agent/Connect permission, and treat any agent that executes code from outside your organization, ephemeral pull request runners above all, as sitting on the wrong side of this boundary.
Why build servers keep coming up
Continuous integration systems are unusually attractive targets: they hold credentials for everything downstream, and they run other people's code by design. CISA added a critical JetBrains TeamCity bug to its exploited-vulnerabilities catalog this week, a flaw that let unauthenticated attackers take over build servers. Nothing indicates the Jenkins issue is being exploited and it is not in CISA's catalog, but the window is not generous: CrowdStrike's 2026 threat hunting report found most public exploits are weaponized within 48 hours.
This briefing is provided by IntelFusions for informational and defensive purposes only. It is based on sources assessed to be reliable at the time of writing, and analytic judgments carry the confidence levels indicated. Indicators of compromise are defanged; re-arm them only in controlled environments. IntelFusions is not affiliated with the organizations named and makes no warranty as to completeness or accuracy.