CVE-2015-7501

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 83.3%, top 0% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 83%
CISA-KEV: Not listedEPSS: 83%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

Red Hat JBoss A-MQ 6.x; BPM Suite (BPMS) 6.x; BRMS 6.x and 5.x; Data Grid (JDG) 6.x; Data Virtualization (JDV) 6.x and 5.x; Enterprise Application Platform 6.x, 5.x, and 4.3.x; Fuse 6.x; Fuse Service Works (FSW) 6.x; Operations Network (JBoss ON) 3.x; Portal 6.x; SOA Platform (SOA-P) 5.x; Web Server (JWS) 3.x; Red Hat OpenShift/xPAAS 3.x; and Red Hat Subscription Asset Manager 1.3 allow remote attackers to execute arbitrary commands via a crafted serialized Java object, related to the Apache Commons Collections (ACC) library.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
82(Track*)
EG Risk 82/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation83% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
99.6%
KEV
Not listed

Published

November 9, 2017

Last Modified

May 13, 2026

Vendor Advisories for CVE-2015-7501(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(19)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrh-maven35-apache-commons-collections4-0:4.0-7.3.el72020-10-19redhat
redhatrubygem-openshift-origin-routing-daemon-0:0.26.6.1-1.el6op2016-08-24redhat
redhatjbossas2016-02-03redhat
redhatpatch2016-01-14redhat
redhatjakarta-commons-collections-0:3.2-2jpp.42015-12-21redhat
redhatpatch2015-12-07redhat
redhatpatch2015-12-07redhat
redhattomcat2015-12-04redhat
redhatpicketbox-0:4.1.2-1.Final_redhat_1.1.ep6.el52015-12-02redhat
redhatpicketbox-0:4.1.2-1.Final_redhat_1.1.ep6.el72015-12-02redhat
redhatpatch2015-12-02redhat
redhatpicketbox-0:4.1.2-1.Final_redhat_1.1.ep6.el62015-12-02redhat
redhatjboss-ec2-eap-0:7.5.5-3.Final_redhat_3.ep6.el62015-12-02redhat
redhatapache-commons-collections-eap6-0:3.2.1-16.redhat_5.1.ep6.el72015-12-01redhat
redhatjakarta-commons-collections-0:3.2.1-5.ep5.el62015-12-01redhat
redhatrh-java-common-apache-commons-collections-0:3.2.1-21.13.el72015-11-30redhat
redhatapache-commons-collections-0:3.2.1-22.el7_22015-11-30redhat
redhatjakarta-commons-collections-0:3.2.1-3.5.el6_72015-11-30redhat
redhatpatch2015-11-24redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 1 ecosystem)

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 11× in last 7d / 22× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 01:19 UTCEG score recompute
  2. 2026-07-23 00:21 UTCEG score recompute
  3. 2026-07-22 21:59 UTCEG score recompute
  4. 2026-07-22 14:04 UTCEPSS rescore
  5. 2026-07-21 15:21 UTCEPSS rescore
  6. 2026-07-21 15:21 UTCEPSS rescore
  7. 2026-07-20 17:03 UTCEPSS rescore
  8. 2026-07-19 02:26 UTCEPSS rescore
  9. 2026-07-19 02:26 UTCEPSS rescore
  10. 2026-07-18 10:00 UTCEPSS rescore
  11. 2026-07-16 16:59 UTCEPSS rescore
  12. 2026-07-15 16:54 UTCEPSS rescore
  13. 2026-07-15 16:54 UTCEPSS rescore
  14. 2026-07-11 08:23 UTCEPSS rescore
  15. 2026-07-08 15:10 UTCEPSS rescore
  16. 2026-07-07 20:11 UTCOSV refresh
  17. 2026-07-06 16:24 UTCEPSS rescore
  18. 2026-07-04 06:28 UTCEPSS rescore
  19. 2026-06-28 04:53 UTCEPSS rescore
  20. 2026-06-25 13:47 UTCEPSS rescore
  21. 2026-06-25 13:47 UTCEPSS rescore
  22. 2026-06-23 21:30 UTCEPSS rescore
  23. 2026-06-19 07:25 UTCOSV refresh
  24. 2026-06-18 17:50 UTCEPSS rescore
  25. 2026-06-17 17:50 UTCEPSS rescore
Show 36 more
  1. 2026-06-17 17:49 UTCEPSS rescore
  2. 2026-06-15 17:45 UTCEPSS rescore
  3. 2026-06-14 23:14 UTCEPSS rescore
  4. 2026-06-13 22:57 UTCEPSS rescore
  5. 2026-06-12 23:09 UTCEPSS rescore
  6. 2026-06-12 23:09 UTCEPSS rescore
  7. 2026-06-11 13:57 UTCEPSS rescore
  8. 2026-06-11 13:57 UTCEPSS rescore
  9. 2026-06-10 22:15 UTCEPSS rescore
  10. 2026-06-10 13:18 UTCEPSS rescore
  11. 2026-06-08 14:14 UTCEPSS rescore
  12. 2026-06-07 15:22 UTCEPSS rescore
  13. 2026-06-06 13:45 UTCEPSS rescore
  14. 2026-06-05 06:08 UTCEPSS rescore
  15. 2026-06-05 06:08 UTCEPSS rescore
  16. 2026-06-01 13:49 UTCEPSS rescore
  17. 2026-06-01 13:49 UTCEPSS rescore
  18. 2026-05-31 00:14 UTCEPSS rescore
  19. 2026-05-30 17:53 UTCOSV refresh
  20. 2026-05-29 13:41 UTCEPSS rescore
  21. 2026-05-22 21:15 UTCEPSS rescore
  22. 2026-05-21 22:40 UTCEPSS rescore
  23. 2026-05-20 22:37 UTCEPSS rescore
  24. 2026-05-20 22:37 UTCEPSS rescore
  25. 2026-05-20 07:21 UTCVendor advisory
  26. 2026-05-20 03:18 UTCVendor advisory
  27. 2026-05-19 23:16 UTCVendor advisory
  28. 2026-05-19 19:14 UTCVendor advisory
  29. 2026-05-19 15:12 UTCVendor advisory
  30. 2026-05-19 11:10 UTCVendor advisory
  31. 2026-05-19 07:05 UTCVendor advisory
  32. 2026-05-19 03:03 UTCVendor advisory
  33. 2026-05-18 23:00 UTCEG score recompute
  34. 2026-05-18 23:00 UTCVendor advisory
  35. 2026-05-18 21:30 UTCEPSS rescore
  36. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCianxtianxt/CVE-2015-7501
    First seen Feb 21, 2020

    (CVE-2015-7501)JBoss JMXInvokerServlet 反序列化漏洞

    Open source ↗

Frequently asked(5)

What is CVE-2015-7501?
CVE-2015-7501 is a critical vulnerability published on November 9, 2017. Red Hat JBoss A-MQ 6.x; BPM Suite (BPMS) 6.x; BRMS 6.x and 5.x; Data Grid (JDG) 6.x; Data Virtualization (JDV) 6.x and 5.x; Enterprise Application Platform 6.x, 5.x, and 4.3.x; Fuse 6.x; Fuse Service Works (FSW) 6.x; Operations Network (JBoss ON) 3.x; Portal 6.x; SOA Platform (SOA-P) 5.x; Web…
When was CVE-2015-7501 disclosed?
CVE-2015-7501 was first published in the National Vulnerability Database on November 9, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2015-7501 actively exploited?
CVE-2015-7501 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2015-7501?
CVE-2015-7501 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2015-7501?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2015-7501, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2015-7501

Explore →

Is Your Infrastructure Affected by CVE-2015-7501?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.