CVE-2016-0691

LOWNVD 3.33.3—

3.3

Unspecified vulnerability in the RDBMS Security component in Oracle Database Server 11.2.0.4, 12.1.0.1, and 12.1.0.2 allows local users to affect integrity via unknown vectors, a different vulnerability than CVE-2016-0690.

CVSS v3: 3.3
EG Score: 3.3(medium)
EPSS: 35.1%
KEV: Not listed

Published

April 21, 2016

Last Modified

May 6, 2026

References (4)

secalert_us@oraclehttp://www.oracle.com/technetwork/security-advisory/cpuapr2016v3-2985753.html
secalert_us@oraclehttp://www.securitytracker.com/id/1035590
af854a3a-2127-422b-91ae-364da2661108http://www.oracle.com/technetwork/security-advisory/cpuapr2016v3-2985753.html
af854a3a-2127-422b-91ae-364da2661108http://www.securitytracker.com/id/1035590

Data Freshness Timeline

(refreshed 8× in last 7d / 20× 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-06-08 14:14 UTCEPSS rescore
2026-06-07 15:22 UTCEPSS rescore
2026-06-06 13:45 UTCEPSS rescore
2026-06-05 22:44 UTCEPSS rescore
2026-06-05 06:08 UTCEPSS rescore
2026-06-05 06:08 UTCEPSS rescore
2026-06-04 13:10 UTCEPSS rescore
2026-06-04 13:10 UTCEPSS rescore
2026-06-02 20:10 UTCEPSS rescore
2026-06-01 13:49 UTCEPSS rescore
2026-06-01 13:49 UTCEPSS rescore
2026-05-31 22:28 UTCEPSS rescore
2026-05-31 22:28 UTCEPSS rescore
2026-05-31 00:14 UTCEPSS rescore
2026-05-29 13:41 UTCEPSS rescore
2026-05-28 13:42 UTCEPSS rescore
2026-05-28 13:42 UTCEPSS rescore
2026-05-27 13:38 UTCEPSS rescore
2026-05-27 13:38 UTCEPSS rescore
2026-05-26 13:41 UTCEPSS rescore

Frequently asked(5)

What is CVE-2016-0691?

CVE-2016-0691 is a low vulnerability published on April 21, 2016. Unspecified vulnerability in the RDBMS Security component in Oracle Database Server 11.2.0.4, 12.1.0.1, and 12.1.0.2 allows local users to affect integrity via unknown vectors, a different vulnerability than CVE-2016-0690.

When was CVE-2016-0691 disclosed?

CVE-2016-0691 was first published in the National Vulnerability Database on April 21, 2016, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2016-0691 actively exploited?

CVE-2016-0691 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 35.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2016-0691?

CVE-2016-0691 has a CVSS v3 base score of 3.3 (NVD).

How do I remediate CVE-2016-0691?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-0691, 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-2016-0691

Explore →

Is Your Infrastructure Affected by CVE-2016-0691?

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

Start Free Scan →Browse All CVEs

CVE-2016-0691

📅 Published

🔄 Last Modified

🔗 References (4)