CVE-2026-48920: Jenkins Email Extension Plugin Attackers Able To Control Email Vulnerability
HIGHCVE-2026-48920 is a HIGH (CVSS 8.8) attackers able to control email vulnerability (CWE-73: External Control of File Name or Path) affecting Jenkins Email Extension Plugin libraries in the Maven ecosystem. The issue involves attackers able to control email content may specify `file:` urls for images to read arbitrary files from jenkins controller filesystem. Remediation is available by upgrading affected packages to version 1933.1935.v276319e3cc47.
CVE-2026-48920 at a Glance
Security Impact
CVSS: 8.8
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).
How to Fix CVE-2026-48920
To remediate this vulnerability, upgrade all affected Jenkins Email Extension Plugin dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
<dependency>
<groupId>org.jenkins-ci.plugins</groupId>
<artifactId>email-ext</artifactId>
<version>1933.1935.v276319e3cc47</version>
</dependency>
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree -Dincludes=org.jenkins-ci.plugins
How to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-48920, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree -Dincludes=org.jenkins-ci.plugins
Analyze the terminal output to locate any version of Jenkins Email Extension Plugin in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1933.1935.v276319e3cc47), your application is affected.
Note: The mvn dependency:tree -Dincludes=org.jenkins-ci.plugins command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-73: External Control of File Name or Path, where the product allows user input to control or influence paths or file names that are used in filesystem operations. In Jenkins Email Extension Plugin, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-48920 Affected Jenkins Email Extension Plugin Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
org.jenkins-ci.plugins:email-ext
|
Maven |
< 1933.1935.v276319e3cc47
|
1933.1935.v276319e3cc47
|
References
Frequently Asked Questions
What is CVE-2026-48920?
Which Jenkins Email Extension Plugin versions are affected?
What version fixes CVE-2026-48920?
Is email-ext affected?
What is the CVSS score of CVE-2026-48920?
What CWE is associated with CVE-2026-48920?
How can I check Maven dependencies for CVE-2026-48920?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-mq58-m26g-46gp",
"modified" : "2026-07-01T19:42:14Z",
"published" : "2026-05-27T15:33:26Z",
"aliases" : [ "CVE-2026-48920" ],
"summary" : "Jenkins Email Extension Plugin: Attackers able to control email content may specify `file:` URLs for images to read arbitrary files from Jenkins controller filesystem",
"details" : "Jenkins Email Extension Plugin 1933.v45cec755423f and earlier includes a feature that allows inlining images as `base64` in email content by setting the `data-inline` attribute. No restrictions are placed on the image URLs that can be inlined.\n\nThis allows attackers able to control the email content to specify `file:` URLs for images to read arbitrary files from the Jenkins controller filesystem.\n\nThe feature allowing inlining images as `base64` in email content by setting the `data-inline` attribute is removed from Email Extension Plugin 1933.1935.v276319e3cc47.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "org.jenkins-ci.plugins:email-ext"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1933.1935.v276319e3cc47"
} ]
} ]
} ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-48920"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/jenkinsci/email-ext-plugin"
}, {
"type" : "WEB",
"url" : "https://www.jenkins.io/security/advisory/2026-05-27/#SECURITY-3705"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-73" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-07-01T19:42:14Z",
"nvd_published_at" : "2026-05-27T15:16:31Z"
}
}