The GitLab fix for the CVSS 10.0 regex flaw is a patch to Ruby that GitLab applies only in its own packages, so installations running their own Ruby also need Ruby 3.3.13, 3.4.12 or 4.0.9.
Jenkins 2.588 and LTS 2.580.2 fix 15 core flaws, including XStream code execution
EditorialBy TrustList Editorial
The Jenkins project's 28 October advisory fixes 13 high and 2 medium flaws in core, among them deserialization code execution, an unauthenticated admin-account race in the setup wizard and agent launchers that skip admin approval.
- DevOps
- Application Security
- Cybersecurity
- Credential Management
About Jenkins 2.588 and LTS 2.580.2 fix 15 core flaws, including XStream code execution
Jenkins 2.588 and LTS 2.580.2 fix 15 core flaws, including XStream code execution
28 October 2026: The Jenkins project published a security advisory on 28 October covering 15 vulnerabilities in Jenkins core, 13 rated high and 2 medium (CVE-2026-117612 to CVE-2026-117626). Every weekly release up to 2.587 and every LTS release up to 2.580.1 is affected. The fixes are in Jenkins 2.588 and LTS 2.580.2. The advisory covers core only, so plugins need their own checks.
The flaws that lead to code execution or takeover
- XStream deserialization (SECURITY-4125, CVE-2026-117612): a custom converter did not apply Jenkins' class filter to classes named in a resolves-to attribute. Anyone with Overall/Read and a permission that can post config.xml, such as Item/Configure, View/Configure or Agent/Configure, can execute code. The fix also adds XStream type permissions, which can be switched off with a system property if it breaks something.
- Setup wizard race (SECURITY-4122, CVE-2026-117618): while the initial account is being replaced during setup, an endpoint meant to stop administrators locking themselves out lets an unauthenticated attacker create an administrator account. New installations exposed to a network during setup are the ones at risk.
- Agent launchers without approval (SECURITY-4123, CVE-2026-117614): old agent configurations are converted into Command Agent Launcher Plugin launchers without administrator approval, so Agent/Configure is enough to run code on the controller.
- Old Data Monitor injection (SECURITY-4226, CVE-2026-117620): a user with Overall/Read can plant a warning that, when an administrator acts on it, overwrites a user account's data, including the password on controllers using Jenkins' own user database.
- Files and paths (SECURITY-4187, 4188 and 4248): renaming an item follows symlinks and can expose arbitrary controller files; path traversal in agent names lets Overall/Read load any config.xml as an agent and overwrite files; and a race in artifact extraction from parallel Pipeline branches writes arbitrary files. The last was reported through the Jenkins bug bounty programme sponsored by the European Commission.
The rest of the list
Other high-rated issues include stored cross-site scripting in the workspace browser, agent error messages and breadcrumb tooltips (mitigated where Content Security Policy is enforced, on 2.539 and LTS 2.541.1 or later), a stored XSS through collection type checks, a root-element bypass in XStream whose confirmed impact is limited to creating user records, and "remember me" cookies that can be obtained with an API token and outlive its revocation (SECURITY-4189). The two medium issues expose the HTTP proxy configuration and file names in $JENKINS_HOME to users with Overall/Read.
Who should move first
Many of these need some permission, but in Jenkins Overall/Read is often granted to every signed-in user, and Item/Configure to every developer. Controllers where many people can configure jobs or agents carry the most exposure, as do controllers reachable from the internet. The project does not report exploitation in the wild. After upgrading, administrators should check whether the new XStream type permissions break any plugin before reaching for the opt-out, and review API tokens that were revoked recently, since "remember me" cookies obtained with them stay valid until the upgrade.
Related on TrustList:
- Alpine rebuilds GitLab after CVE-2026-97229 attempt; the fix needs patched Ruby
- Gheist campaign uses stolen GitHub tokens to dump Actions secrets
- PingCAP breach: TiDB Cloud users told to replace API keys now
Sources
- Jenkins Security Advisory 2026-10-28, 28 October 2026
Categories & features
- DevOps
- Application Security
- Cybersecurity
- Credential Management
TrustList Weekly
The week in software and IT, in one email
The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.
You may be interested in
Wiz Research tracked more than 13,500 planted ci-sync branches from over 850 compromised accounts; GitHub's approval hold stops the workflows in public repositories but not in private ones or GitHub Enterprise Server.
An attacker used a compromised GitHub account and leaked credentials for four weeks, copying customer contacts, contract terms, SQL editor text and encrypted API keys. PingCAP says the databases themselves were not reached.
Seven are rated high, including an account takeover through OAuth2 auto-linking and fork workflows that receive repository secrets. Every release up to 28.2.0 is affected; there is no backport line.
We classified our 198 security advisories from 22 September to 28 October. 64 described attacks already under way, edge devices led, half of KEV listings came within five days of a fix, and the CVSS score was a weak guide to which ones mattered.
Besides the bundled OpenJPEG overflow, the Python imaging library published 39 more advisories fixed in 13.0.0, including code execution from one crafted FlashPix file. One Arrow memory leak is still unfixed.
CVE-2026-111497 is rated 9.2 by Google and hits every Brotli release from 1.0.3 to 1.2.0. Envoy, the PyPI packages and Debian have shipped fixes; Ubuntu still ranks it medium.
Four AWS bulletins on 22 October: Strands Agents A2A servers leaked conversation history between callers, SAM CLI's Terraform hook allowed command injection, Athena exposed query text, and aws-c-mqtt could crash clients.
More on TrustList
Everything here links back to the same verified catalogue. Pick your next stop.
- More DevOpsThe ranking for this subject
- CompaniesAgencies, consultancies and IT service providers, ranked by verified reviews.
- ProductsSoftware and SaaS with pricing, features, integrations and alternatives.
- AwardsAnnual recognition decided by verified reviews and an independent jury.
- LaunchesNew products and releases, voted up by the community every day.
- AI ModelsBenchmark scores and community ratings for every major model.
- RequestsBuyers describe what they need; vendors respond directly.
- PeopleReviewers, authors and makers with public profiles.
- ComparePut up to four listings side by side before you shortlist.