CVE-2026-49410 tinyhumansai CVE debrief

Who should care

Defenders responsible for OpenHuman deployments should assess exposure and prioritize verification of their versions. They should also monitor for suspicious activity and implement additional security measures to prevent exploitation.

Why it matters

CVE-2026-49410 is a high-severity CSRF vulnerability in OpenHuman that could allow an attacker to switch a user's active local session to their backend account, exposing subsequent agent actions, memory writes, and Telegram messages. Defenders should prioritize verification of their versions and monitor for suspicious activity.

• Potential exposure of subsequent agent actions to an attacker
• Potential exposure of memory writes associated with the compromised session to an attacker
• Potential exposure of Telegram messages associated with the compromised session to an attacker
• Verification of OpenHuman version and potential upgrade to 0.56.0

Technical summary

The vulnerability exists in the OpenHuman agent harness, specifically in the unauthenticated GET /auth/telegram loopback callback. An attacker can exploit this by tricking a user into visiting a malicious page, which can switch the user's active local session to the attacker's backend account. This could expose subsequent agent actions, memory writes, and Telegram messages associated with that session to the attacker. Defenders should prioritize verifying if they are using OpenHuman versions before 0.56.0 and upgrading to 0.56.0 if vulnerable. They should also monitor for suspicious activity, such as unexpected session changes or unauthorized access to agent actions and Telegram messages.

Defensive priority

Defenders should prioritize verifying if they are using OpenHuman versions before 0.56.0 and upgrading to 0.56.0 if vulnerable. They should also monitor for suspicious activity, such as unexpected session changes or unauthorized access to agent actions and Telegram messages.

Recommended defensive actions

• Verify if using OpenHuman versions before 0.56.0 and upgrade to 0.56.0 if vulnerable
• Monitor for suspicious activity, such as unexpected session changes or unauthorized access to agent actions and Telegram messages
• Implement additional security measures, such as validating browser fetch metadata and request origin
• 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 NVD entry provide details about the vulnerability, including its description, CVSS score, and affected versions. However, there is limited information about potential exploits or attacks in the wild.

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.