Skip to main content
VulnerabilityPublished Updated

CVE-2025-15141: Halo · Information Disclosure

Affects HaloSource CVE Database V5

0

Public exploit available · CVSS 2.3 Low.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score
2.3Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubhalo/halopkg:github/halo/haloOther threatsAffected
  • 2.21.0 – 2.21.10
11 affected builds
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Given the absence of official patches, organizations should implement compensating controls to mitigate risk. First, restrict network access to the /actuator endpoint by implementing firewall rules or network segmentation to limit exposure to trusted internal networks only. Employ web application firewalls (WAFs) to detect and block suspicious requests targeting the /actuator path. Monitor logs for unusual or repeated access attempts to this endpoint to identify potential reconnaissance activity. If possible, disable or remove the /actuator endpoint or the Configuration Handler component if it is not required for operational purposes. Maintain up-to-date backups and monitor vendor communications for any forthcoming patches or advisories. Additionally, conduct regular security assessments and penetration tests focusing on Halo deployments to identify any related weaknesses. Finally, educate system administrators about this vulnerability and the importance of minimizing exposure of management endpoints.

Description

A vulnerability was determined in Halo up to 2.21.10. This issue affects some unknown processing of the file /actuator of the component Configuration Handler. Executing a manipulation can lead to information disclosure. The attack may be performed from remote. This attack is characterized by high complexity. The exploitability is assessed as difficult. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

References

Community reviews

Loading reviews…