Skip to main content

Chronosphere Chronocollector CVE-2026-0239

| EUVDEUVD-2026-30091 MEDIUM
Exposure of Sensitive System Information to an Unauthorized Control Sphere (CWE-497)
2026-05-13 palo_alto GHSA-3544-2m8c-rh83
4.9
CVSS 4.0 · Vendor: palo_alto
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain adjacent network access
  2. Delivery
    Identify Chronocollector service port
  3. Exploit
    Send unauthenticated request to collector endpoint
  4. Execution
    Service returns sensitive information without credential check
  5. Impact
    Attacker captures disclosed data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection System info exposure prevention
Exploitation Conditions

The attacker must have adjacent network access (AV:A) to the host running Chronosphere Chronocollector - this means being on the same broadcast domain, VLAN, or directly connected subnet. Internet-based exploitation is not possible without prior network pivot. No authentication is required (PR:N) and no user interaction is needed (UI:N), so any deployment of Chronocollector versions prior to v0.116.0 that is reachable from an adjacent network segment is exploitable without credentials. There are no known non-default configuration prerequisites mentioned in available data. Exploitation is constrained solely by the adjacent network requirement, meaning exposure is highest in flat network architectures where monitoring agents share segments with untrusted hosts.

Impact

The CVSS 4.0 base score of 4.9 (Medium) appropriately reflects the adjacent-only attack vector (AV:A), which meaningfully constrains real-world exploitability compared to a fully remote vulnerability. Confidentiality impact on the vulnerable component is rated High (VC:H) with no integrity or availability impact. The CVSS 4.0 supplemental modifier V:C (Value Density: Concentrated) elevates concern, suggesting exposed data may be high-value. Countering this, the EPSS score of 0.02% at the 6th percentile indicates very low exploitation probability based on historical patterns. SSVC confirms Exploitation: none, Automatable: no (consistent with the adjacent-network constraint), and Technical Impact: partial. The Exploit Maturity modifier E:U (Unreported) aligns with no known public exploit. The CVSS urgency rating of Amber and response effort of Moderate suggest a planned patching cadence is appropriate rather than emergency response. Overall, this is a genuine but bounded risk: organizations should patch to v0.116.0 but need not treat this as a critical emergency absent evidence of targeting.

Exploit ScenarioDerived

An attacker who has gained a foothold on the same network segment as a Chronosphere Chronocollector instance - for example, via a compromised host in a monitoring VLAN - sends an unauthenticated HTTP request to the collector's service endpoint. The service responds with sensitive information without requiring credentials, potentially exposing internal configuration, credentials, or telemetry metadata. No public exploit code has been identified at time of analysis, but the low complexity (AC:L, AT:N) suggests exploitation requires no special skill once network proximity is achieved.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 08, 2026

Unauthenticated information disclosure in Palo Alto Networks' Chronosphere Chronocollector exposes sensitive data to any attacker with adjacent network access to the collector service endpoint. All versions from 0.0.0 up to v0.116.0 are affected, with the fix released in v0.116.0. No public exploit code has been identified at time of analysis and CISA has not added this to the KEV catalog, but the CVSS 4.0 Value Density modifier of 'Concentrated' (V:C) suggests the data at risk may include high-value material such as credentials or configuration secrets.

RemediationAI

Upgrade Chronosphere Chronocollector to version v0.116.0 or later, which resolves this vulnerability per the EUVD affected version range. The vendor advisory at https://security.paloaltonetworks.com/CVE-2026-0239 should be consulted for any additional deployment guidance. If immediate patching is not feasible, implement network-layer access controls to restrict which hosts or subnets can reach the Chronocollector service port - because the attack vector is Adjacent (AV:A), enforcing strict network segmentation (e.g., dedicated monitoring VLANs with ACLs) would prevent exploitation by blocking access from untrusted adjacent segments. Be aware that overly restrictive ACLs on the collector port could interrupt metrics ingestion pipelines, so changes should be validated in a staging environment. Host-based firewall rules on the collector host are a secondary option with less operational disruption.

Affected VersionsENISA

Chronosphere Chronocollector 0.0.0 <v0.116.0

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Chronosphere Chronocollector is a metrics and observability data collection agent (CPE: cpe:2.3:a:palo_alto_networks:chronosphere_chronocollector:*:*:*:*:*:*:*:*) used in cloud-native monitoring infrastructure. The root cause is classified as CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere), meaning the service exposes internal system or application data through an interface that should not surface it - typically via an API endpoint, debug route, or metadata service that lacks authentication enforcement. The CVSS 4.0 vector confirms no authentication (PR:N) and no user interaction (UI:N) are required, and the attack vector is Adjacent (AV:A), meaning the attacker must be on the same network segment, broadcast domain, or directly connected subnet - not reachable over the open internet without prior network access.

Know when Chronosphere Chronocollector gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (palo_alto) PRIMARY 4.9 MEDIUM
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:U/AU:N/R:U/V:C/RE:M/U:Amber

Primary rating from Vendor (palo_alto) · only source for this CVE.

CVSS VectorVendor: palo_alto

Attack Vector
Adjacent
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
CVSS changed
May 13, 2026 - 19:22 NVD
4.9 (MEDIUM)
CVE Published
May 13, 2026 - 18:27 nvd
UNKNOWN (no severity yet)

DescriptionCVE.org

An information disclosure vulnerability in the Chronosphere Chronocollector enables an unauthenticated attacker with network access to the collector service to retrieve sensitive information.

Threat Intelligence Overview

EPSS Score
0.0%
Top 94% exploitable
Social Media
1
Sightings
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Controlled
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

24
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +24
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy