Vulnerability in the Oracle Communications Convergent Charging Controller product of Oracle Communications (component: Prov IF). Supported versions that are affected are 15.0.0.0.0 and 15.2.0.0.0. Difficult to exploit vulnerability allows high privileged attacker with network access via HTTP to compromise Oracle Communications Convergent Charging Controller. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of Oracle Communications Convergent Charging Controller. CVSS 3.1 Base Score 6.4 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
CVE-2026-61143
Score 6.4 from GitHub Security Advisory published 2026-07-22. a secondary CVSS source baseline 6.4; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.4
- EG Score
- 6.4(high)
- EG Risk
- 33(Track)EG Risk 33/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 computedSeverity64% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 11.8%
- KEV
- Not listed
Published
July 21, 2026
Last Modified
July 23, 2026
References (1)
- secalert_us@oraclehttps://www.oracle.com/security-alerts/cpujul2026.html
Vendor Advisories for CVE-2026-61143(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(4)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× 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.
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:21 UTCEG score recompute
- 2026-07-22 14:24 UTCEG score recompute
- 2026-07-22 14:24 UTCGHSA enrichment
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 22:18 UTCEG score recompute
- 2026-07-21 22:03 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-640 · CWE-284 · CWE-304
- CVE-2012-5686EG 9.8EPSS 91%CRITICAL
- CVE-2012-5618EG 9.8CRITICAL
- CVE-2010-5305EG 9.8EPSS 92%CRITICAL
- CVE-2011-3172NVD 5.4EG 9.8MEDIUM
- CVE-2014-10059EG 9.8CRITICAL
- CVE-2014-10053EG 9.8CRITICAL
- CVE-2014-10050EG 9.8CRITICAL
- CVE-2015-0150EG 9.8CRITICAL
- CVE-2014-2048EG 9.8CRITICAL
- CVE-2013-0422EG 9.8 KEVEPSS 100%CRITICAL
Frequently asked(5)
What is CVE-2026-61143?
When was CVE-2026-61143 disclosed?
Is CVE-2026-61143 actively exploited?
What is the CVSS score of CVE-2026-61143?
How do I remediate CVE-2026-61143?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-61143
Is Your Infrastructure Affected by CVE-2026-61143?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.