CVE-2026-13575 TOKUHIROM CVE debrief

Who should care

Defenders responsible for Perl applications using HTTP::Session versions before 0.54 should assess exposure and prioritize upgrading to version 0.54 or later. Additionally, system administrators and security teams managing memcached installations should review access controls and monitor for suspicious activity.

Why it matters

The vulnerability in HTTP::Session versions before 0.54 allows for memcached command injection, potentially leading to unauthorized access or data manipulation. Defenders should prioritize verifying the version in use, upgrading if necessary, and reviewing memcached access controls.

• Verify the version of HTTP::Session in use and upgrade to version 0.54 or later if vulnerable.
• Review and restrict access to memcached to prevent exploitation.
• Monitor for suspicious activity related to memcached commands.

Technical summary

The vulnerability exists in HTTP::Session versions before 0.54 for Perl, specifically in the HTTP::Session::Store::CHI module. The session id from the client's cookie is not filtered and reaches the CHI cache unchanged. When using a memcached driver, this can lead to command injection due to the lack of checks for control characters in the session id. The vulnerability can be exploited by an attacker to execute arbitrary commands on the memcached server, potentially leading to unauthorized access or data manipulation. Defenders should prioritize verifying the version in use and upgrading to version 0.54 or later if vulnerable. Additionally, defenders should review and restrict access to memcached to prevent (

Defensive priority

Defenders should prioritize verifying the version of HTTP::Session in use and upgrading to version 0.54 or later if vulnerable. Additionally, defenders should review and restrict access to memcached to prevent exploitation.

Recommended defensive actions

• Verify the version of HTTP::Session in use and upgrade to version 0.54 or later if vulnerable.
• Review and restrict access to memcached to prevent exploitation.
• Monitor for suspicious activity related to memcached commands.
• 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.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.

Evidence notes

The CVE record and source references indicate that HTTP::Session versions before 0.54 are vulnerable to memcached command injection. However, the corpus does not provide information on known affected or fixed versions beyond the vulnerable range.

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.