dbcve.org
Chronosphere CollectorApplication · Paloaltonetworks

CVE-2026-0239

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-13
Fix available
A fix is available. Upgrade to 0.116.0 or later.
See remediation →
70/100
Remediation priority · Elevated
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
An information disclosure vulnerability in the Chronosphere Chronocollector enables an unauthenticated attacker with network access to the collector service to retrieve sensitive information.

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 information disclosure vulnerability in Chronosphere Chronocollector allows an unauthenticated attacker with network access to the collector service to retrieve sensitive information. The vulnerability stems from insufficient access controls on the collector component, enabling unauthenticated network-based exfiltration of data that should be protected.

MitigationImplement authentication and proper access controls on the Chronocollector service, and restrict network access to trusted sources to prevent unauthenticated information disclosure.

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
Chronosphere CollectorApplication
Affected:< 0.116.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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:A/AC:L/PR:N/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 Chronosphere Collector installation
    Locate the Chronosphere Collector service or binary in your environment. Check for processes named 'chronocollector' or files under typical installation paths such as /opt/chronosphere/ or /usr/local/bin/chronocollector. Query running services or container images for the collector component.
    Affected if Chronosphere Collector is present and running in the environment
  2. Determine installed collector version
    Run the command 'chronocollector --version' or check the package/version file in the installation directory. Compare the version number against the affected range of versions prior to 0.116.0.
    Affected if The installed version is lower than 0.116.0
  3. Verify network exposure of collector service
    Check network configuration to determine if the Chronocollector service port is listening on a network interface accessible to unauthenticated attackers. Use commands like 'netstat -tlnp' or 'ss -tlnp' to identify listening ports, and review firewall or security group rules controlling access to the collector.
    Affected if The collector service is bound to a non-localhost interface and accessible from untrusted network paths
  4. Inspect access control configuration
    Examine the Chronocollector configuration files for authentication settings and access control rules. Look for authentication enforcement flags, API key requirements, or allowed source IP configurations in the collector configuration.
    Affected if Authentication is disabled or access controls are not enforced, allowing unauthenticated requests to the collector endpoint

You are affected if Chronosphere Collector versions below 0.116.0 are running and the collector service is network-accessible without authentication or proper access controls.

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 0.116.0 or later
Fixed in 0.116.0
Interim mitigation

Implement authentication and proper access controls on the Chronocollector service, and restrict network access to trusted sources to prevent unauthenticated information disclosure.

Recommended fix Moderate confidence

Chronosphere Collector version 0.116.0 or later

  1. 1. Identify all deployed instances of Chronosphere Collector in your environment
  2. 2. Check the current version of each Collector instance using the collector's version command or administration interface
  3. 3. Plan an upgrade to version 0.116.0 or later for all affected Collectors (versions below 0.116.0)
  4. 4. Review the Chronosphere upgrade documentation for Collector version 0.116.0
  5. 5. Execute the upgrade procedure according to Chronosphere's official upgrade guide
  6. 6. After upgrading, verify the Collector is running version 0.116.0 or higher
  7. 7. Confirm the vulnerability is remediated by testing that unauthenticated network requests no longer return sensitive information

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

Fix this in Chronosphere Collector 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-0239 — 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-0239 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