CVE-2026-73276 Erlang CVE debrief

Who should care

Defenders responsible for systems using Erlang's OTP for HTTP request handling should assess exposure and prioritize patching or mitigating this vulnerability. This includes operators, platform administrators, vulnerability management teams, and security teams. They should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance, and plan vendor-supported updates or mitigations through normal change控制.

Why it matters

CVE-2026-73276 is a high-severity vulnerability in Erlang's OTP that could allow for HTTP Request Smuggling attacks. Defenders should prioritize patching or mitigating this vulnerability, especially in systems that use Erlang's OTP for HTTP request handling.

• Potential for HTTP Request Smuggling attacks
• Possible impact on system availability and security
• Need for patching or mitigating affected OTP versions
• Importance of monitoring and filtering HTTP requests

Technical summary

The vulnerability is caused by the gracefulness code ignoring cases that should be rejected, resulting in possible HTTP Request Smuggling opportunities. This issue affects OTP from OTP 22.2 before OTP 27.3.4.17, from OTP 28.0 before OTP 28.5.0.6, and from OTP 29.0 before OTP 29.0.6, corresponding to inets from 7.1.2 before 9.3.2.7, from 9.4 before 9.6.2.3, and from 9.7 before 9.7.2. The vulnerability has a CVSS score of 8.3 and is considered HIGH severity. Defenders should prioritize patching or mitigating this vulnerability, especially in systems that use Erlang's OTP for HTTP request handling.

Defensive priority

Defenders should prioritize patching or mitigating this vulnerability, especially in systems that use Erlang's OTP for HTTP request handling.

Recommended defensive actions

• Assess exposure and prioritize patching for OTP versions from 22.2 before 27.3.4.17, from 28.0 before 28.5.0.6, and from 29.0 before 29.0.6
• Review and update inventory to identify systems using affected OTP versions
• Implement compensating controls, such as monitoring and filtering, for HTTP requests
• 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
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected versions. The CVE record was published on 2026-09-01T15:17:25.367Z and has not been modified since then. The NVD entry provides additional information on the vulnerability, including its severity and potential impact. However, the source detail is limited, and defenders should verify the affected scope and severity through other means.

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.