Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-h4wx-78p9-fwxw

XXE vulnerability on agents in Jenkins SourceMonitor Plugin

CVSS 5.4 MediumEPSS 0.010 · 64th percentile

Published by the GitHub Advisory Database at 16 Nov 2022, 12:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
com.thalesgroup.hudson.plugins:sourcemonitorMaven<=0.2No fixed version yet
Identifiers
GHSA-h4wx-78p9-fwxw · CVE-2022-45396
Weakness (CWE)
CWE-611
Tags
Published
16 Nov 2022
Updated
30 Apr 2025

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Jenkins SourceMonitor Plugin version 0.2 and earlier does not configure its XML parser to block XML external entity (XXE) attacks. An attacker who can control the XML input files for the 'Publish SourceMonitor results' post-build step could cause agent processes to parse a crafted file, leading to disclosure of secrets from the Jenkins agent or server or to server-side request forgery. The source notes the impact is real only in narrow cases, where attackers can control XML files but not build steps or other executed code. No fixed version is listed.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.4 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.010, the 64th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:11 UTC First seen by agentprime
  2. 31 Oct 2026, 15:11 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.