GPU VulnDB

Database/Control plane, storage & DevOps

Jenkins Ivy Report Plugin: XXE in Ivy report parsing gives an authenticated user file read on the controller

CVE-2026-70448Control plane, storage & DevOpscurated

Impact

The plugin parses Ivy report files without disabling external entities, so a user who can influence a build's Ivy report can make the Jenkins controller resolve attacker-chosen entities. That yields file reads on the controller and outbound requests from it - and a CI controller in a GPU fleet is usually holding registry credentials, kubeconfigs, and cluster service-account tokens, which makes controller file read a credential-theft problem rather than an information leak. Exposure is entirely conditional on having this specific plugin installed; most Jenkins instances do not. NVD scores it 7.1 with low privileges required, so an ordinary job-configuring user is enough.

Who can reach it

Authenticated Jenkins user with enough permission to run or configure a job that produces an Ivy report the plugin then parses. Not reachable unauthenticated, and not reachable at all if the plugin is not installed.

What to do

First check whether the plugin is installed at all (Manage Jenkins - Plugins); if it is not, there is nothing to do. The Jenkins advisory covers version 1.2 and earlier - consult SECURITY-3899 for whether a fixed release exists, and do not assume one from this record. If no fix is listed, uninstall the plugin; either way the change requires a controller restart, which interrupts running builds but touches no GPU nodes.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.