Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-47045: Vulnerability in the JDBC component of Oracle Database Server

32
Routine
MEDIUM 6.8UPGRADE

CVE-2026-47045 is a medium-severity flaw (CVSS 6.8) affecting database server. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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. Easily exploitable vulnerability allows high privileged attacker having None privilege with network access via Oracle Net to compromise JDBC. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of JDBC. C

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score6.8 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededHigh
User interactionRequired
EPSS exploit chance0.4% (top 67%)
CISA exploited listNo
WeaknessCWE-601
Published2026-07-21
Last modified2026-10-24
Publisher (CNA): Oracle · Vendor: oracle

Share: LinkedIn · X · Reddit

Last updated 2026-10-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

oracle database server UPGRADE
Affected: >= 19.3 and <= 19.31 · >= 21.3 and <= 21.22 · >= 23.4 and <= 23.26.2
Fixed in: newer than 23.26.2
Safe to downgrade to: a release before 19.3
1. Check installed version
apt-cache policy database-server || rpm -q database-server || database-server --version
2. UPGRADE to newer than 23.26.2 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade database-server
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade database-server
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 19.3 (Debian / Ubuntu)
apt-cache madison database-server sudo apt install database-server=<VERSION_BEFORE_19.3> sudo apt-mark hold database-server
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list database-server sudo dnf downgrade database-server-<VERSION_BEFORE_19.3> sudo dnf versionlock add database-server
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-47045?

database server: upgrade to newer than 23.26.2. Exact commands for each OS are on this page.

Is CVE-2026-47045 being exploited?

CVE-2026-47045 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-47045 affect?

CVE-2026-47045 affects database server. Severity is medium (CVSS 6.8). 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. Easily exploitable vulnerability allows high privileged attacker having None privilege with

How urgent is CVE-2026-47045?

Priority 32/100. No elevated risk signals yet.

Software pages

Oracle Database vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.