CVE-2026-74835 Erlang CVE debrief

Who should care

Defenders responsible for Erlang OTP deployments should assess exposure and prioritize patching affected versions. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify and apply patches, assess exposure, and monitor for potential exploitation attempts.

Why it matters

CVE-2026-74835 is a high-severity vulnerability in Erlang OTP that could allow attackers to bypass body-size limits on chunked requests. Defenders should prioritize patching affected versions, assessing exposure, and monitoring for exploitation attempts.

• Verify and apply patches to prevent potential exploitation
• Assess exposure in your environment to determine affected systems
• Monitor for potential exploitation attempts to detect potential attacks

Technical summary

The inets application HTTP server httpd fails to enforce a configured body-size limit on chunked requests. This issue affects OTP from OTP 17.0 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 5.10 before 9.3.2.7, from 9.4 before 9.6.2.3, and from 9.7 before 9.7.2. The vulnerability allows attackers to bypass body-size limits on chunked requests, potentially leading to denial-of-service or other security issues. Defenders should prioritize verifying and applying patches for affected OTP versions, assessing exposure in their environments, and monitoring for potential exploitation attempts.

Defensive priority

Defenders should prioritize verifying and applying patches for affected OTP versions, assessing exposure in their environments, and monitoring for potential exploitation attempts.

Recommended defensive actions

• Verify and apply patches for affected OTP versions
• Assess exposure in your environment
• Monitor for potential exploitation attempts
• Review compensating controls for exposed systems
• Check relevant monitoring, detection, and logs for exposed assets
• 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 on the vulnerability, including its description, CVSS score, and affected versions. However, the extent of exploitation and impact remains unknown. Defenders should verify and apply patches for affected OTP versions, assess exposure in their environments, and monitor for potential exploitation attempts. The CVE Program record and NVD detail page offer source-provided CVE metadata and vulnerability assessments.

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.