dbcve.org
Endpoint SecurityApplication · Elastic

CVE-2026-56152

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-01
Fix available
A fix is available. Upgrade to 8.19.13 / 9.2.7 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable Zero-click 7 weeks old

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
Incorrect Authorization (CWE-863) in Elastic Defend can lead to unauthorized information disclosure via Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1). Under certain conditions, a low-privileged authenticated user can access response action data that they are not authorized to view.

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

An incorrect authorization vulnerability (CWE-863) in Elastic Defend allows low-privileged authenticated users to access response action data they are not authorized to view, due to functionality not being properly constrained by access control lists (CAPEC-1). This enables unauthorized information disclosure.

MitigationApply available Elastic security patches or updates for Elastic Defend, and review/audit user role configurations and access control policies to ensure response action data is properly restricted.

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
Endpoint SecurityApplication
Affected:>= 8.6.0, < 8.19.13>= 9.0.0, < 9.2.7>= 9.3.0, < 9.3.2

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

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/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. Identify Elastic Defend installation
    Check if Elastic Defend integration is enabled by navigating to Kibana > Integrations > Installed integrations, or run 'elastic-agent list' on hosts with the agent installed
    Affected if Elastic Defend integration is present in the environment
  2. Determine installed Elastic Defend version
    In Kibana, go to Stack Management > Installed Plugins or check the Elastic Agent policy version; alternatively, check the elastic-Defend package version via the Elasticsearch _plugins endpoint
    Affected if Version falls within any of the affected ranges: 8.6.0 to 8.19.12, 9.0.0 to 9.2.6, or 9.3.0 to 9.3.1
  3. Verify response actions are accessible
    Check if response actions (isolation, file quarantine, process termination) are available to users by reviewing the Actions menu in the Elastic Defend console for a low-privileged test user account
    Affected if Low-privileged users can view or execute response actions without proper role restrictions
  4. Review user role permissions for response action data
    In Kibana, navigate to Stack Management > Security > Roles and inspect role configurations, specifically checking if roles assigned to low-privilege users have unintended access to response action APIs or data endpoints
    Affected if Roles without explicit response action permissions nevertheless grant access to response action data or APIs

Environment is affected if Elastic Defend is installed with a version in the affected ranges AND low-privileged users can access response action data they should not be authorized to view.

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.

dbcve · scoped
Upgrade available Upgrade to 8.19.13 / 9.2.7 / 9.3.2 or later
Fixed in 8.19.139.2.79.3.2
Interim mitigation

Apply available Elastic security patches or updates for Elastic Defend, and review/audit user role configurations and access control policies to ensure response action data is properly restricted.

Recommended fix Moderate confidence

8.19.13 (for 8.x), 9.2.7 (for 9.0.x), or 9.3.2 (for 9.3.x)

  1. 1. Identify the current Elastic Endpoint Security version installed in your environment
  2. 2. Determine which version branch you are running (8.x, 9.0.x, or 9.3.x)
  3. 3. For 8.x versions (>=8.6.0, <8.19.13): Upgrade to version 8.19.13 or later
  4. 4. For 9.0.x versions (>=9.0.0, <9.2.7): Upgrade to version 9.2.7 or later
  5. 5. For 9.3.x versions (>=9.3.0, <9.3.2): Upgrade to version 9.3.2 or later
  6. 6. After upgrade, verify that low-privileged users can no longer access unauthorized response action data
  7. 7. Review user roles and permissions to ensure proper ACLs are configured

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Endpoint Security Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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