How severe is CVE-2019-0227?

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

Which packages are affected by CVE-2019-0227?

CVE-2019-0227 affects the following packages: org.apache.axis:axis (Maven), axis:axis (Maven). Ecosystems affected: Maven.

How do I fix CVE-2019-0227?

No patched version of org.apache.axis:axis has shipped for CVE-2019-0227 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

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

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

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

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

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

Yes. There are 4 known exploit references for CVE-2019-0227, including 1 documented proof-of-concept exploit on Exploit-DB and 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2019-0227?

CVE-2019-0227 has an EPSS (Exploit Prediction Scoring System) score of 91.9%, placing it in the 100th 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2019-0227?

CVE-2019-0227 is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

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

CVE-2019-0227 was published on May 1, 2019 and was last updated on March 15, 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-0227 — axis

HIGH

CVE-2019-0227 is a high-severity (CVSS 7.5) Server-Side Request Forgery (SSRF) vulnerability in org.apache.axis:axis. 4 public exploit references exist, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

Server Side Request Forgery in Apache Axis

Also known asGHSA-h9gj-rqrw-x4fq

Published

May 1, 2019

Updated

Mar 15, 2026

Affected

2 pkgs

Patched

See advisory

Exploits

4 known

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

EPSS Exploitation Probability

via FIRST.org ↗

91.9%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

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

How urgent is this, really

CVE-2019-0227 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 396,257 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected

☕org.apache.axis:axis☕axis:axis

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 Server Side Request Forgery (SSRF) vulnerability affected the Apache Axis 1.4 distribution that was last released in 2006. Security and bug commits commits continue in the projects Axis 1.x Subversion repository, legacy users are encouraged to build from source. The successor to Axis 1.x is Axis2, the latest version is 1.7.9 and is not vulnerable to this issue.

Affected Packages

2 total

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.axis:axis`	all versions	No fix
☕Maven	`axis:axis`	all versions	No fix

Affected Products

37 products · 77 configurations

Application

axisapache

1 version

1.4

Application

agile engineering data managementoracle

1 version

6.2.1.0

Application

agile product lifecycle managementoracle

1 version

9.3.3

Application

application testing suiteoracle

2 versions

13.2.0.113.3.0.1

Application

big data discoveryoracle

1 version

1.6

Application

communications asap cartridgesoracle

2 versions

7.27.3

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-46682remotemultiple

Apache Axis 1.4 - Remote Code Execution

by David Yesland · Apr 9, 2019

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.axis:axis, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of org.apache.axis:axis has shipped for CVE-2019-0227 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2019-0227 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.5/10CVSS v3 base

Vector breakdown

Attack Vector

Adjacent

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

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

CWE Classification

CWE-918Server-Side Request Forgery (SSRF)

Weaponization

No known public exploit tooling found.

Timeline

First exploit

Apr 9, 2019

Disclosed

May 1, 2019

Last updated

Mar 15, 2026

Identifiers

CVE-2019-0227

GHSA-h9gj-rqrw-x4fq

References

Advisorysecurity.netapp.com Advisorynvd.nist.gov Fixoracle.com Fixoracle.com Fixoracle.com Fixoracle.com Fixoracle.com Fixoracle.com Fixoracle.com Fixoracle.com Weblists.apache.org Weblists.apache.org Weboracle.com Weblists.apache.org Weblists.apache.org Webrhinosecuritylabs.com Websecurity.netapp.com Evidencerhinosecuritylabs.com

Related vulnerabilities

Also affects axis

This CVE is high severity; 2 of 6 other CVEs affecting axis are rated as high or higher (top: critical).

CVE-2023-51441CVE-2023-40743CVE-2007-2353CVE-2012-5784CVE-2018-8032CVE-2014-3596

Same weakness: CWE-918

This CVE is high severity — higher than any of the other 2 CVEs with CWE-918 (highest there: moderate).

CVE-2026-115886CVE-2026-62197Browse all CWE-918

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedMar 15, 2026

CVE-2019-0227 — axis

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