dbcve.org
Life Sciences Central DesignerApplication · Oracle

CVE-2026-21974

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vulnerability in the Oracle Life Sciences Central Designer product of Oracle Health Sciences Applications (component: Platform). The supported version that is affected is 7.0.1.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Life Sciences Central Designer. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Oracle Life Sciences Central Designer accessible data. CVSS 3.1 Base Score 5.3 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is an information disclosure vulnerability in Oracle Life Sciences Central Designer 7.0.1.0 where an unauthenticated remote attacker can gain unauthorized read access to a subset of accessible data via HTTP. The attack requires no authentication or user interaction and exploits the Platform component.

MitigationApply the Oracle Critical Patch Update that addresses CVE-2026-21974, or upgrade to a patched version of Oracle Life Sciences Central Designer. Until a patch is available, restrict network access to the Platform component to trusted sources only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Life Sciences Central DesignerApplication
Affected:= 7.0.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Oracle Life Sciences Central Designer is installed
    Locate the installation directory or check for running processes related to Oracle Life Sciences Central Designer. Common installation paths include Oracle middleware home directories. Check for processes named 'Oracle Central Designer' or similar in running process lists.
    Affected if The product is not installed - then not affected. If installed, proceed to version check.
  2. Verify the installed version is 7.0.1.0
    Check the version of Oracle Life Sciences Central Designer. Look in the installation directory for a version file, check the about/management console, or query the application directly. The exact version must be 7.0.1.0 to be affected.
    Affected if Installed version equals 7.0.1.0 exactly - proceed to next check. Other versions are not affected by this CVE.
  3. Confirm the Platform component HTTP interface is accessible
    Attempt to access the Platform component via HTTP/HTTPS. This is typically exposed through the application server (WebLogic, etc.) on ports 7001/7002 or similar. Check if HTTP endpoints respond without authentication.
    Affected if The Platform component HTTP interface responds to requests without requiring authentication - the vulnerability condition exists.
  4. Determine network exposure of the Platform component
    Check the network binding and firewall rules for the server hosting the Platform component. Determine if the HTTP port is bound to 0.0.0.0 or an externally accessible IP, and whether network access controls restrict it to trusted sources only.
    Affected if The Platform component HTTP interface is accessible from untrusted network segments or the internet - the vulnerability is exploitable from those locations.

A user is affected if they are running exactly version 7.0.1.0 of Oracle Life Sciences Central Designer AND the Platform component HTTP interface is accessible from untrusted networks without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Oracle Critical Patch Update that addresses CVE-2026-21974, or upgrade to a patched version of Oracle Life Sciences Central Designer. Until a patch is available, restrict network access to the Platform component to trusted sources only.

Fix this in Life Sciences Central Designer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-21974 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-21974 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data