How severe is CVE-2019-16573?

CVE-2019-16573 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-16573?

CVE-2019-16573 affects the following packages: com.alauda.jenkins.plugins:alauda-devops-pipeline (Maven). Ecosystems affected: Maven.

How do I fix CVE-2019-16573?

The records we use list no patched version of com.alauda.jenkins.plugins:alauda-devops-pipeline for CVE-2019-16573. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

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

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

How do I mitigate CVE-2019-16573 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-16573 actively exploited in the wild?

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

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

CVE-2019-16573 is classified as Cross-Site Request Forgery (CSRF) (CWE-352). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2019-16573 was published on December 17, 2019 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

HIGH severity

CVE-2019-16573 — alauda-devops-pipeline

HIGH

CVE-2019-16573 is a high-severity (CVSS 8.8) Cross-Site Request Forgery (CSRF) vulnerability in com.alauda.jenkins.plugins:alauda-devops-pipeline. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Jenkins Alauda DevOps Pipeline Plugin vulnerable to cross-site request forgery

Also known asGHSA-pv4c-rj4h-gr9m

Published

Dec 17, 2019

Updated

Oct 24, 2026

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

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

☕com.alauda.jenkins.plugins:alauda-devops-pipeline

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

A cross-site request forgery vulnerability in Jenkins Alauda DevOps Pipeline Plugin 2.3.2 and earlier allows attackers to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.alauda.jenkins.plugins:alauda-devops-pipeline`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

alauda devops pipelinejenkins

≤ 2.3.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.alauda.jenkins.plugins:alauda-devops-pipeline, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of com.alauda.jenkins.plugins:alauda-devops-pipeline for CVE-2019-16573. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
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

O3 Security · Impact-Aware SCA

Is CVE-2019-16573 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

8.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

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

CWE Classification

CWE-352Cross-Site Request Forgery (CSRF)

Weaponization

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

Timeline

Disclosed

Dec 17, 2019

Last updated

Oct 24, 2026

Identifiers

CVE-2019-16573

GHSA-pv4c-rj4h-gr9m

References

Advisoryopenwall.com Advisoryjenkins.io · 2019 12 17 Advisorynvd.nist.gov · CVE 2019 16573

Related vulnerabilities

Also affects alauda-devops-pipeline

This CVE is high severity — higher than any of the other 1 CVE affecting alauda-devops-pipeline (highest there: moderate).

CVE-2019-16574

Same weakness: CWE-352

This CVE is high severity; 2 of 7 other CVEs with CWE-352 are rated as high or higher (top: high).

CVE-2026-96629CVE-2026-118266CVE-2026-113796CVE-2026-84312CVE-2026-62322CVE-2026-107809CVE-2026-107848Browse all CWE-352

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2019-16573 — alauda-devops-pipeline

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

Remediation status

Mitigate without a patch

Frequently Asked Questions

Is CVE-2019-16573 in your dependencies?