Insufficiently Protected CredentialsWeakness · CWE-522

CVE-2026-23927

MEDIUM · 5.1 CVSS v4.0 Published 2026-05-06

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

57/100

Remediation priority · Elevated

Remotely reachable Zero-click

Official description

NVD · unedited

A user able to connect to Agent 2 can inject an Oracle TNS connection string via the 'service' parameter. This can lead to Agent 2 connecting to an attacker-controlled server and leaking Oracle database credentials if they are saved in a named session.

Technical summary

dbcve analysis · moderate confidence

This is an injection vulnerability in Agent 2 where the 'service' parameter accepts Oracle TNS connection strings without proper validation. An authenticated user can supply a malicious TNS connection string directing Agent 2 to an attacker-controlled server, causing it to leak stored Oracle database credentials from named sessions to the attacker's server.

MitigationImplement strict input validation on the 'service' parameter to restrict TNS connections to authorized servers only, and avoid storing Oracle credentials in named sessions or encrypt them at rest.

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

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: High
Authentication: X
User interaction: None
Scope: X

CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:L/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected?

dbcve checks

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

Identify if Agent 2 is installed

Locate the Agent 2 installation directory or check system inventory for this product. Common locations may include /opt/agent2, C:\Program Files\Agent2, or check running processes for 'agent2' or 'Agent 2' entries.

Affected if Agent 2 software is present on the system
Determine the installed version of Agent 2

Check the installed version using the product's --version flag, about dialog, or version file in the installation directory. Compare this version against any known fixed versions provided by the vendor.

Affected if The installed version is lower than the fixed version (if known) or cannot be determined to be patched
Verify if Oracle TNS connection functionality is enabled

Inspect Agent 2 configuration files (such as config.xml, settings.conf, or similar) for the 'service' parameter or TNS connection module settings. Check whether Oracle database connectivity features are configured or active.

Affected if The TNS connection / service parameter feature is enabled or configured in Agent 2
Inspect stored named sessions for Oracle credentials

Examine the session storage directory for named session files. Look for session configuration files, credential stores, or connection profiles that contain Oracle database credentials. Search for patterns indicating stored usernames and passwords for Oracle connections.

Affected if Named sessions exist that contain unencrypted or plaintext Oracle database credentials
Review network configuration for outbound Oracle connections

Check Agent 2 logs or network configuration for recent outbound Oracle TNS connections. Examine the 'service' parameter values used in connection attempts to identify any pointing to unauthorized or unexpected destinations.

Affected if TNS connections have been made to servers not in your approved Oracle server list

A user is affected if Agent 2 is installed with the service parameter/TNS feature enabled and has stored Oracle credentials in named sessions that could be exfiltrated to an attacker-controlled server.

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

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Implement strict input validation on the 'service' parameter to restrict TNS connections to authorized servers only, and avoid storing Oracle credentials in named sessions or encrypt them at rest.

Have this fixed Scoped from the published advisory

Consultation3.0 h
Implementation6.0 h
Testing4.0 h
Review / QA2.0 h

15.0 hours of engineering $2,640

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

support.zabbix.com
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2026-23927?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 5.1 Medium

Exploit likelihood EPSS, next 30 days 0.2%

Remediation

Need this fixed?

Have this fixed 15 hrs · Moderate

Typical engagement from $2,640

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2026-23927 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References