CVE-2026-116283 Kameleo CVE debrief

Who should care

Defenders responsible for Kameleo deployments should assess exposure and prioritize upgrading to version 5.2.0 if vulnerable. Defenders should prioritize verifying exposure of Kameleo versions up to 5.0.1.26 and upgrading to version 5.2.0 if vulnerable to prevent information disclosure. Affected operators, platforms, vulnerability-management, and security teams should be aware of the vulnerability and take necessary actions. The Local API profilescomponent

Why it matters

Defenders should prioritize verifying exposure of Kameleo versions up to 5.0.1.26 and upgrading to version 5.2.0 if vulnerable to prevent information disclosure.

• Verify exposure of Kameleo versions up to 5.0.1.26
• Upgrade to version 5.2.0 if vulnerable
• Monitor Local API profiles component for unusual activity

Technical summary

The vulnerability affects Kameleo versions up to 5.0.1.26 and is caused by a weakness in the Local API profiles component. This issue allows for remote exploitation and information disclosure. Upgrading to version 5.2.0 mitigates this vulnerability. The vulnerability is a weakness in the Local API profiles component, allowing for remote exploitation and information disclosure. Defenders should prioritize verifying exposure of Kameleo versions up to 5.0.1.26 and upgrading to version 5.2.0 if vulnerable. The affected product context and defensive impact should be considered.

Defensive priority

Defenders should prioritize verifying exposure of Kameleo versions up to 5.0.1.26 and upgrading to version 5.2.0 if vulnerable.

Recommended defensive actions

• Verify Kameleo version and check for exposure
• Upgrade to version 5.2.0 if vulnerable
• Monitor Local API profiles component for unusual activity
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability, affected versions, and mitigation. However, additional information from the vendor and other sources may be necessary for a comprehensive understanding.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.