dbcve.org
Life Sciences Empirica SignalApplication · Oracle

CVE-2026-21997

HIGH · 8.5 CVSS v3.1 Published 2026-04-21
Fix available
A fix is available. Upgrade to after 9.2.3 or later.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable 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 Empirica Signal product of Oracle Life Science Applications (component: Common Core). Supported versions that are affected are 9.2.1-9.2.3. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Life Sciences Empirica Signal. While the vulnerability is in Oracle Life Sciences Empirica Signal, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Life Sciences Empirica Signal accessible data as well as unauthorized read access to a subset of Oracle Life Sciences Empirica Signal accessible data. CVSS 3.1 Base Score 8.5 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/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 · high confidence

A vulnerability in Oracle Life Sciences Empirica Signal (Common Core component, versions 9.2.1-9.2.3) allows low-privileged attackers with network access via HTTP to create, delete, or modify critical data and read a subset of accessible data. The scope changed due to potential impact on additional products.

MitigationApply the Oracle patch when available. Until then, restrict network access to the application and consider WAF rules to mitigate exploitation attempts.

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 Empirica SignalApplication
Affected:>= 9.2.1, <= 9.2.3

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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/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. Identify if Oracle Life Sciences Empirica Signal is installed
    Look for Empirica Signal installation directories, running services, or web application processes on the system. Check common application server directories or Oracle installation paths.
    Affected if The software is present on the system
  2. Determine the installed version of Empirica Signal
    Access the application admin interface, check version files in the installation directory, or query the system information endpoint if available. Compare the version number against the affected range.
    Affected if The installed version is 9.2.1, 9.2.2, or 9.2.3
  3. Verify the Common Core component is enabled
    Check the application configuration or module settings to confirm the Common Core component is active. This is the specific component referenced in the CVE.
    Affected if Common Core is enabled and accessible within the application
  4. Confirm network accessibility via HTTP
    Verify the application is reachable over HTTP/HTTPS from the network. The CVE specifies the attack vector requires network access via HTTP.
    Affected if The application is network-accessible via HTTP
  5. Check for low-privileged user accounts
    Review user accounts and roles configured in the application. The CVE specifically notes low-privileged attackers can exploit this flaw.
    Affected if Low-privileged user accounts exist in the system that could be leveraged for exploitation

A user is affected if Oracle Life Sciences Empirica Signal version 9.2.1, 9.2.2, or 9.2.3 is installed with the Common Core component enabled and accessible over the network.

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
Upgrade available Upgrade to a release after 9.2.3
Interim mitigation

Apply the Oracle patch when available. Until then, restrict network access to the application and consider WAF rules to mitigate exploitation attempts.

Fix this in Life Sciences Empirica Signal Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-21997 — 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-21997 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