How severe is CVE-2019-10361?

CVE-2019-10361 has a CVSS score of 3.3/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2019-10361?

CVE-2019-10361 affects the following packages: org.jenkins-ci.plugins.m2release:m2release (Maven). Ecosystems affected: Maven.

How do I fix CVE-2019-10361?

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

How do I detect CVE-2019-10361 in my Maven dependencies?

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

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2019-10361 actively exploited in the wild?

No public exploit code has been indexed for CVE-2019-10361 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-2019-10361?

CVE-2019-10361 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 41th 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-2019-10361?

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

When was CVE-2019-10361 published, and has it been updated?

CVE-2019-10361 was published on May 24, 2022 and was last updated on February 16, 2024. 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

LOW severity

CVE-2019-10361 — m2release

LOWFix: jenkinsci/m2release-plugin@a2e7f2b

CVE-2019-10361 is a low-severity (CVSS 3.3) CWE-522 vulnerability in org.jenkins-ci.plugins.m2release:m2release. A fix is available for org.jenkins-ci.plugins.m2release:m2release — see the affected versions and patch details below.

Jenkins Maven Release Plug-in Plugin stored credentials in plain text

Published

May 24, 2022

Updated

Feb 16, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs41th percentile — riskier than 41% 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

1 pkg affected

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

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 Maven Release Plug-in Plugin stored credentials unencrypted in its global configuration file org.jvnet.hudson.plugins.m2release.M2ReleaseBuildWrapper.xml on the Jenkins controller. These credentials could be viewed by users with access to the Jenkins controller file system.

Maven Release Plug-in Plugin now stores credentials encrypted.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins.m2release:m2release`	all versions	0.15.0`org.jenkins-ci.plugins.m2release:m2release:0.15.0`

Affected Products

1 product · 1 configurations

Application

m2releasejenkins

≤ 0.14.0

range

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.m2release:m2release, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins.m2release:m2release to 0.15.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-10361 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Jenkins Maven Release Plug-in Plugin stored credentials unencrypted in its global configuration file `org.jvnet.hudson.plugins.m2release.M2ReleaseBuildWrapper.xml` on the Jenkins controller. These credentials could be viewed by users with access to the Jenkins controller file system. Maven Release Plug-in Plugin now stores credentials encrypted.

O3 Security · Impact-Aware SCA

Is CVE-2019-10361 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

3.3/10CVSS v3 base

Vector breakdown

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-522CWE-522

Weaponization

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

Timeline

Disclosed

May 24, 2022

Last updated

Feb 16, 2024

Identifiers

CVE-2019-10361

References

Advisorynvd.nist.gov · CVE 2019 10361 Webgithub.com · a2e7f2bb82640a9d3641265a19c86ba141a7e79c Webjenkins.io · 2019 07 31 Webopenwall.com

Related vulnerabilities

Also affects m2release

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

CVE-2019-10360CVE-2019-16549CVE-2019-16550CVE-2019-10359

Same weakness: CWE-522

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

CVE-2026-105769CVE-2026-118763CVE-2026-116683GHSA-vqqp-x5qm-5qp4Browse all CWE-522

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedFeb 16, 2024

CVE-2019-10361 — m2release

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-2019-10361 in your dependencies?