How severe is CVE-2022-20614?

CVE-2022-20614 has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-20614?

CVE-2022-20614 affects the following packages: org.jenkins-ci.plugins:mailer (Maven), org.jenkins-ci.plugins:mailer (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-20614?

Update org.jenkins-ci.plugins:mailer to 408.vd726a or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-20614 is resolved across your whole dependency graph.

How do I detect CVE-2022-20614 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:mailer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-20614 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2022-20614 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-20614 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-20614?

CVE-2022-20614 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 67th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-20614?

CVE-2022-20614 is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-20614 published, and has it been updated?

CVE-2022-20614 was published on January 12, 2022 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2022-20614 — mailer

MEDIUMFix: jenkinsci/mailer-plugin@5e6051f

CVE-2022-20614 is a medium-severity (CVSS 4.3) CWE-862 vulnerability in org.jenkins-ci.plugins:mailer. A fix is available for org.jenkins-ci.plugins:mailer — see the affected versions and patch details below.

Incorrect Permission Assignment for Critical Resource in Jenkins Mailer Plugin

Also known asGHSA-558x-h7rg-997v

Published

Jan 12, 2022

Updated

Oct 24, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk+0.04%

Lower risk than most CVEs67th percentile — riskier than 67% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

☕org.jenkins-ci.plugins:mailer☕org.jenkins-ci.plugins:mailer

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Jenkins Mailer Plugin prior to 408.vd726a_1130320 and 1.34.2 does not perform a permission check in a method implementing form validation.

This allows attackers with Overall/Read access to use the DNS used by the Jenkins instance to resolve an attacker-specified hostname.

Additionally, this form validation method does not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability.

Mailer Plugin 408.vd726a_1130320 and 1.34.2 requires POST requests and Overall/Administer permission for the affected form validation method.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:mailer`	≥ 391.ve4a38c1bcf4b&&< 408.vd726a	408.vd726a`org.jenkins-ci.plugins:mailer:408.vd726a`
☕Maven	`org.jenkins-ci.plugins:mailer`	all versions	1.34.2`org.jenkins-ci.plugins:mailer:1.34.2`

Affected Products

2 products · 3 configurations

Application

mailerjenkins

< 1.34.2

1 version

391.ve4a_38c1b_cf4b_

Application

communications cloud native core automated test suiteoracle

1 version

1.9.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:mailer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:mailer to 408.vd726a or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-20614 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

Jenkins Mailer Plugin prior to 408.vd726a_1130320 and 1.34.2 does not perform a permission check in a method implementing form validation. This allows attackers with Overall/Read access to use the DNS used by the Jenkins instance to resolve an attacker-specified hostname. Additionally, this form validation method does not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability. Mailer Plugin 408.vd726a_1130320 and 1.34.2 requires POST requests and Overall/Administer permission for the affected form validation method.

O3 Security · Impact-Aware SCA

Is CVE-2022-20614 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

4.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

CWE Classification

CWE-862CWE-862

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Jan 12, 2022

Last updated

Oct 24, 2026

Identifiers

CVE-2022-20614

GHSA-558x-h7rg-997v

References

Advisoryopenwall.com Advisoryjenkins.io · 2022 01 12 Advisorynvd.nist.gov · CVE 2022 20614 Fixoracle.com · cpuapr2022 Webgithub.com · 5e6051fae61a43564e22aa89cb24ed8a42a26052

Related vulnerabilities

Also affects mailer

This CVE is medium severity; 3 of 4 other CVEs affecting mailer are rated as high or higher (top: high).

CVE-2020-2252CVE-2018-8718CVE-2017-2651CVE-2022-20613

Same weakness: CWE-862

This CVE is medium severity; 4 of 4 other CVEs with CWE-862 are rated as high or higher (top: high).

CVE-2026-103002CVE-2026-94619CVE-2026-85737CVE-2026-94618Browse all CWE-862

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2022-20614 — mailer

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2022-20614 in your dependencies?