How severe is CVE-2019-12728?

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

Which packages are affected by CVE-2019-12728?

CVE-2019-12728 affects the following packages: org.grails:grails-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2019-12728?

Update org.grails:grails-core to 3.3.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-12728 is resolved across your whole dependency graph.

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

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

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

Yes. There are 1 known exploit references for CVE-2019-12728, including 1 in-the-wild exploitation 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-12728?

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

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

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

CVE-2019-12728 was published on June 4, 2019 and was last updated on October 20, 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-12728 — grails-core

HIGH

CVE-2019-12728 is a high-severity (CVSS 8.1) CWE-494 vulnerability in org.grails:grails-core. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.grails:grails-core — see the affected versions and patch details below.

Incorrect Resource Transfer Between Spheres in Grails

Also known asGHSA-pmxf-4v8c-rwr7

Published

Jun 4, 2019

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs62th percentile — riskier than 62% 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.grails:grails-core

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

Grails before 3.3.10 used cleartext HTTP to resolve the SDKMan notification service. NOTE: users' apps were not resolving dependencies over cleartext HTTP.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.grails:grails-core`	all versions	3.3.10`org.grails:grails-core:3.3.10`

Affected Products

1 product · 1 configurations

Application

grailsgrails

< 3.3.10

range

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.

Grails before 3.3.10 used cleartext HTTP to resolve the SDKMan notificat…

github.comNVDJul 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.grails:grails-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.grails:grails-core to 3.3.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-12728 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

Grails before 3.3.10 used cleartext HTTP to resolve the SDKMan notification service. NOTE: users' apps were not resolving dependencies over cleartext HTTP.

O3 Security · Impact-Aware SCA

Is CVE-2019-12728 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

8.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

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

CWE Classification

CWE-494CWE-494

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

OpenSSF Scorecard

Package health score

grails-core

6.0/10

Code-Review5/10

Maintained10/10

Branch-Protection3/10

Assessed Nov 2, 2026

Timeline

Disclosed

Jun 4, 2019

First exploit

Jul 21, 2021

Last updated

Oct 20, 2026

Identifiers

CVE-2019-12728

GHSA-pmxf-4v8c-rwr7

References

Advisoryobjectcomputing.com · possible grails mitm vulnerability Advisorynvd.nist.gov · CVE 2019 12728 Evidencegithub.com

Related vulnerabilities

Also affects grails-core

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

CVE-2018-1000529

Same weakness: CWE-494

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

CVE-2026-113717CVE-2026-86063CVE-2026-107812CVE-2026-102930CVE-2026-12259GHSA-xhcr-cqfr-m3hvCVE-2026-55697Browse all CWE-494

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 20, 2026

CVE-2019-12728 — grails-core

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