CVE-2026-47061

MEDIUMPre-NVD 5.65.6—
EchelonGraph scoreHIGH confidence

Score 5.6 from GitHub Security Advisory published 2026-07-22. a secondary CVSS source baseline 5.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.6EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.6Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Vulnerability in the JDBC component of Oracle Database Server. Supported versions that are affected are 19.3-19.31, 21.3-21.22 and 23.4.0-23.26.2. Difficult to exploit vulnerability allows unauthenticated attacker with access to the physical communication segment attached to the hardware where the JDBC executes to compromise JDBC. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in JDBC, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all JDBC accessible data. CVSS 3.1 Base Score 5.6 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N).

CVSS v3
5.6
EG Score
5.6(high)
EG Risk
25(Track)
EG Risk 25/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
Severity56% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

July 21, 2026

Last Modified

July 23, 2026

References (1)

Vendor Advisories for CVE-2026-47061(1)

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

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 18× in last 7d / 25× 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-31 08:34 UTCEG score recompute
  2. 2026-07-31 08:34 UTCGHSA enrichment
  3. 2026-07-30 16:28 UTCEPSS rescore
  4. 2026-07-30 07:51 UTCEG score recompute
  5. 2026-07-30 07:51 UTCGHSA enrichment
  6. 2026-07-30 01:30 UTCEPSS rescore
  7. 2026-07-29 06:25 UTCEG score recompute
  8. 2026-07-29 06:25 UTCGHSA enrichment
  9. 2026-07-28 15:37 UTCEPSS rescore
  10. 2026-07-28 05:41 UTCEG score recompute
  11. 2026-07-28 05:41 UTCGHSA enrichment
  12. 2026-07-27 14:13 UTCEPSS rescore
  13. 2026-07-27 04:54 UTCEG score recompute
  14. 2026-07-27 04:54 UTCGHSA enrichment
  15. 2026-07-26 04:11 UTCEG score recompute
  16. 2026-07-26 04:11 UTCGHSA enrichment
  17. 2026-07-25 14:18 UTCEPSS rescore
  18. 2026-07-24 14:17 UTCEPSS rescore
  19. 2026-07-23 14:18 UTCEPSS rescore
  20. 2026-07-23 03:17 UTCEG score recompute
  21. 2026-07-22 15:50 UTCEG score recompute
  22. 2026-07-22 15:49 UTCGHSA enrichment
  23. 2026-07-22 14:08 UTCEPSS rescore
  24. 2026-07-21 21:56 UTCEG score recompute
  25. 2026-07-21 21:38 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-47061?
CVE-2026-47061 is a medium vulnerability published on July 21, 2026. Vulnerability in the JDBC component of Oracle Database Server. Supported versions that are affected are 19.3-19.31, 21.3-21.22 and 23.4.0-23.26.2. Difficult to exploit vulnerability allows unauthenticated attacker with access to the physical communication segment attached to the hardware where the…
When was CVE-2026-47061 disclosed?
CVE-2026-47061 was first published in the National Vulnerability Database on July 21, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47061 actively exploited?
CVE-2026-47061 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.3% of all scored CVEs.
What is the CVSS score of CVE-2026-47061?
CVE-2026-47061 has a CVSS v3 base score of 5.6 (NVD).
How do I remediate CVE-2026-47061?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47061, 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

Explore the affected products and dependency analysis for CVE-2026-47061

Explore →

Is Your Infrastructure Affected by CVE-2026-47061?

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

Start Free Scan →Browse All CVEs