CVE-2018-11039 — Spring Framework (versions 5.0.x prior to 5.0.7, versions 4.3.x prior to 4.3.18, and…

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

• Documented patch — www.oracle.com (NIST National Vulnerability Database)
• Documented mitigation — pivotal.io (NIST National Vulnerability Database)
• Documented patch — www.oracle.com (NIST National Vulnerability Database)
• Documented patch — www.oracle.com (NIST National Vulnerability Database)
• Documented patch — www.oracle.com (NIST National Vulnerability Database)
• Documented patch — www.oracle.com (NIST National Vulnerability Database)
• Documented patch — www.oracle.com (NIST National Vulnerability Database)
• Documented patch — www.oracle.com (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

1. Identify exposed assets running the affected vendor/product/version combinations (Debian Debian Linux, Oracle Agile Product Lifecycle Management, Oracle Application Testing Suite…).
2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
3. Apply the fixed version or the patch documented under Remediation.
4. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 2.75%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

• Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).

Timeline

What happened to this CVE, newest first.

• 2026
• Affected products added · pivotal/spring framework
  Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
• SSVC assessment updated
  Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
• Record published
  Oct 13, 2026
• Fix documented
  Oct 13, 2026 · NIST National Vulnerability Database
• CVSS changed · 5.9
  Oct 13, 2026 · NIST National Vulnerability Database
• Source status changed · → Modified
  Oct 13, 2026 · NIST National Vulnerability Database
• Record created in this database
  Oct 13, 2026 · NIST National Vulnerability Database
• 2018
• CVE published
  Jun 25, 2018 · dell

Source activity

Repeated readings are counted rather than listed.

• 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

10 on the record

• pivotal.io/security/cve-2018-11039
  Mitigation, Vendor Advisory, x_refsource_CONFIRM, NIST National Vulnerability Database
• www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html
  Patch, Third Party Advisory, x_refsource_CONFIRM, NIST National Vulnerability Database
• www.oracle.com/technetwork/security-advisory/cpujan2019-5072801.html
  Patch, Third Party Advisory, x_refsource_CONFIRM, NIST National Vulnerability Database
• www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html
  Patch, Third Party Advisory, x_refsource_MISC, NIST National Vulnerability Database
• www.oracle.com/security-alerts/cpujul2020.html
  Patch, Third Party Advisory, x_refsource_MISC, NIST National Vulnerability Database
• www.oracle.com/security-alerts/cpujan2020.html
  Patch, Third Party Advisory, x_refsource_MISC, NIST National Vulnerability Database
• www.oracle.com/technetwork/security-advisory/cpuapr2019-5072813.html
  Patch, Third Party Advisory, x_refsource_MISC, NIST National Vulnerability Database
• www.oracle.com/security-alerts/cpuoct2021.html
  Patch, Third Party Advisory, x_refsource_MISC, NIST National Vulnerability Database
• www.securityfocus.com/bid/107984
  Broken Link, Third Party Advisory, VDB Entry, vdb-entry, x_refsource_BID, NIST National Vulnerability Database
• lists.debian.org/debian-lts-announce/2021/04/msg00022.html
  Mailing List, Third Party Advisory, mailing-list, x_refsource_MLIST, NIST National Vulnerability Database

Elsewhere on this site

Related CVEs (same products)

• High CVE-2026-87266 Improper Access Control in Oracle Agile Product Lifecycle Management Sep 15, 2026
• High CVE-2026-87254 Improper Access Control in Oracle Agile Product Lifecycle Management Sep 15, 2026
• Medium CVE-2026-87253 Improper Access Control in Oracle Agile Product Lifecycle Management Sep 15, 2026
• High CVE-2026-87257 Improper Access Control in Oracle Agile Product Lifecycle Management Sep 15, 2026
• High CVE-2026-87258 Improper Access Control in Oracle Agile Product Lifecycle Management Sep 15, 2026
• High CVE-2026-87256 Improper Access Control in Oracle Agile Product Lifecycle Management Sep 15, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

• No CWE classification.
• No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
• No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
• No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2018-11039 is "Spring Framework (versions 5.0.x prior to 5.0.7, versions 4.3.x prior to 4.3.18, and…", rated Medium. It affects Debian Linux (Debian); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.9 describes technical severity. EPSS 2.75% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.