LiveActive security incident?Get immediate response
CVE Record

CVE-2026-21939: Vulnerability in the SQLcl component of Oracle Database Server.

Vulnerability in the SQLcl component of Oracle Database Server. Supported versions that are affected are 23.4.0-23.26.0. Difficult to exploit vulnerability allows unauthenticated attacker with logon to the infrastructure where SQLcl executes to compromise SQLcl. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of SQLcl. CVSS 3.1 Base Score 7.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H).

HighCVSS 7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-21939 affects Oracle SQLcl in Oracle Database Server versions 23.4.0 through 23.26.0. An attacker who can access the environment where SQLcl runs could, with user interaction, take over SQLcl. This is not described as internet-remote exploitation, but impact is high if SQLcl is exposed to untrusted local users.

Executive priority

Prioritize remediation for shared admin hosts and systems where SQLcl handles privileged database access. The vulnerability needs local access and user interaction, so urgency is lower than a remote wormable issue but still important because successful exploitation can fully compromise SQLcl.

Technical view

Oracle reports a difficult-to-exploit SQLcl vulnerability with CVSS 3.1 score 7.0: AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H. The attacker needs logon to the infrastructure where SQLcl executes, no privileges, and interaction from another person. Successful exploitation can compromise SQLcl confidentiality, integrity, and availability.

Likely exposure

Exposure is most likely on database administration workstations, jump hosts, CI/CD runners, or servers running Oracle SQLcl 23.4.0 through 23.26.0 where untrusted users can log on or influence user interaction.

Exploitation context

No active exploitation is stated in the provided sources, and the CVE is not marked KEV. Exploitation is constrained by local access, high complexity, and required human interaction. Risk increases in shared administrative environments or where SQLcl is used with sensitive database access.

Researcher notes

The public record does not provide CWE, root-cause detail, proof-of-concept status, or fixed version specifics. Treat the Oracle advisory as authoritative for patch mapping. The phrase “unauthenticated attacker with logon” suggests no SQLcl credentials are needed, but local infrastructure access is required.

Mitigation direction

  • Review Oracle January 2026 Critical Patch Update guidance for this CVE.
  • Update affected SQLcl deployments according to Oracle’s advisory.
  • Restrict logon access to systems where SQLcl executes.
  • Reduce use of SQLcl on shared or untrusted hosts.
  • Train administrators to avoid unexpected SQLcl prompts, files, or workflows.

Validation and detection

  • Inventory SQLcl installations and record version numbers.
  • Confirm whether versions fall within 23.4.0 through 23.26.0.
  • Identify hosts where non-administrators can log on near SQLcl usage.
  • Verify Oracle CPU remediation status for affected assets.
  • Review administrative workflows requiring human interaction with SQLcl.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-21939 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7CVSS 3.1HighCVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H15.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7High
CVSS 3.1 vector shape for CVE-2026-21939Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Oracle CorporationOracle Database Server23.4.0Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.