CVE-2026-47038

LOWPre-NVD 2.72.7—
EchelonGraph scoreMEDIUM confidence

Score 2.7 from GitHub Security Advisory (severity: LOW) published 2026-07-22. a secondary CVSS source baseline 2.7; sources differ by 0.0.

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

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

Vulnerability in the RDBMS 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. Easily exploitable vulnerability allows high privileged attacker having None privilege with network access via Oracle Net to compromise RDBMS. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of RDBMS accessible data. CVSS 3.1 Base Score 2.7 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N).

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

Published

July 21, 2026

Last Modified

August 6, 2026

References (1)

Vendor Advisories for CVE-2026-47038(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 10× in last 7d / 41× 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-09-11 14:53 UTCEPSS rescore
  2. 2026-09-11 09:37 UTCEPSS rescore
  3. 2026-09-10 09:34 UTCEPSS rescore
  4. 2026-09-09 11:05 UTCEG score recompute
  5. 2026-09-09 11:05 UTCGHSA enrichment
  6. 2026-09-08 22:00 UTCEPSS rescore
  7. 2026-09-07 16:01 UTCEPSS rescore
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-05 08:20 UTCEG score recompute
  10. 2026-09-05 08:20 UTCGHSA enrichment
  11. 2026-09-04 05:06 UTCEPSS rescore
  12. 2026-09-02 14:12 UTCEPSS rescore
  13. 2026-09-01 13:54 UTCEPSS rescore
  14. 2026-08-30 19:17 UTCEPSS rescore
  15. 2026-08-30 12:15 UTCEG score recompute
  16. 2026-08-30 12:15 UTCGHSA enrichment
  17. 2026-08-30 01:22 UTCEPSS rescore
  18. 2026-08-28 21:41 UTCEPSS rescore
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-27 12:18 UTCEG score recompute
  21. 2026-08-27 12:18 UTCGHSA enrichment
  22. 2026-08-26 14:46 UTCEPSS rescore
  23. 2026-08-25 13:49 UTCEPSS rescore
  24. 2026-08-24 12:41 UTCEG score recompute
  25. 2026-08-24 12:41 UTCGHSA enrichment
Show 56 more
  1. 2026-08-23 00:19 UTCEPSS rescore
  2. 2026-08-21 23:49 UTCEPSS rescore
  3. 2026-08-21 13:04 UTCEG score recompute
  4. 2026-08-21 13:04 UTCGHSA enrichment
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-18 13:48 UTCEPSS rescore
  8. 2026-08-18 13:20 UTCEG score recompute
  9. 2026-08-18 13:19 UTCGHSA enrichment
  10. 2026-08-17 13:47 UTCEPSS rescore
  11. 2026-08-16 14:56 UTCEPSS rescore
  12. 2026-08-16 02:14 UTCEPSS rescore
  13. 2026-08-15 12:47 UTCEG score recompute
  14. 2026-08-15 12:47 UTCGHSA enrichment
  15. 2026-08-15 01:30 UTCEPSS rescore
  16. 2026-08-13 22:00 UTCEPSS rescore
  17. 2026-08-12 13:51 UTCEPSS rescore
  18. 2026-08-12 13:10 UTCEG score recompute
  19. 2026-08-12 13:10 UTCGHSA enrichment
  20. 2026-08-11 00:00 UTCEPSS rescore
  21. 2026-08-09 13:46 UTCEPSS rescore
  22. 2026-08-09 13:33 UTCEG score recompute
  23. 2026-08-09 13:33 UTCGHSA enrichment
  24. 2026-08-08 16:37 UTCEPSS rescore
  25. 2026-08-06 13:56 UTCEG score recompute
  26. 2026-08-06 13:56 UTCGHSA enrichment
  27. 2026-08-06 13:47 UTCEPSS rescore
  28. 2026-08-05 19:17 UTCEPSS rescore
  29. 2026-08-04 15:10 UTCEPSS rescore
  30. 2026-08-04 10:39 UTCEPSS rescore
  31. 2026-08-04 03:07 UTCEG score recompute
  32. 2026-08-04 03:07 UTCGHSA enrichment
  33. 2026-08-03 10:36 UTCEPSS rescore
  34. 2026-08-02 02:27 UTCEPSS rescore
  35. 2026-08-01 04:16 UTCEPSS rescore
  36. 2026-08-01 03:30 UTCEG score recompute
  37. 2026-08-01 03:29 UTCGHSA enrichment
  38. 2026-07-30 16:28 UTCEPSS rescore
  39. 2026-07-30 01:30 UTCEPSS rescore
  40. 2026-07-29 03:50 UTCEG score recompute
  41. 2026-07-29 03:49 UTCGHSA enrichment
  42. 2026-07-28 15:37 UTCEPSS rescore
  43. 2026-07-27 14:13 UTCEPSS rescore
  44. 2026-07-26 14:54 UTCEPSS rescore
  45. 2026-07-26 14:54 UTCEPSS rescore
  46. 2026-07-26 04:12 UTCEG score recompute
  47. 2026-07-26 04:12 UTCGHSA enrichment
  48. 2026-07-25 14:18 UTCEPSS rescore
  49. 2026-07-24 14:17 UTCEPSS rescore
  50. 2026-07-23 14:18 UTCEPSS rescore
  51. 2026-07-23 03:17 UTCEG score recompute
  52. 2026-07-22 22:48 UTCEG score recompute
  53. 2026-07-22 22:47 UTCGHSA enrichment
  54. 2026-07-22 14:08 UTCEPSS rescore
  55. 2026-07-21 21:58 UTCEG score recompute
  56. 2026-07-21 21:38 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-47038?
CVE-2026-47038 is a low vulnerability published on July 21, 2026. Vulnerability in the RDBMS 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. Easily exploitable vulnerability allows high privileged attacker having None privilege with network access via Oracle Net to compromise RDBMS.…
When was CVE-2026-47038 disclosed?
CVE-2026-47038 was first published in the National Vulnerability Database on July 21, 2026, with the most recent update on August 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47038 actively exploited?
CVE-2026-47038 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 78.9% of all scored CVEs.
What is the CVSS score of CVE-2026-47038?
CVE-2026-47038 has a CVSS v3 base score of 2.7 (NVD).
How do I remediate CVE-2026-47038?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47038, 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-47038

Explore →

Is Your Infrastructure Affected by CVE-2026-47038?

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

Start Free Scan →Browse All CVEs