CVE-2026-49759 remediation guide
Erlang OTP, Red Hat OpenStack Platform 16.2, Red Hat OpenStack Platform 17.1
Stack-based Buffer Overflow vulnerability in Erlang OTP erts (inet_drv) allows an unauthenticated remote attacker to crash the BEAM VM by sending a crafted SCTP ERROR chunk. The sctp_parse_error_chunk function in erts/emulator/drivers/common/inet_drv.c parses SCTP ERROR chunks and writes cause codes into a fixed-size stack-allocated ErlDrvTermData spec[] array without checking bounds. A remote attacker who has established an SCTP association to a listening port can send a single crafted SCTP ERROR chunk containing enough cause codes to overflow the stack buffer, crashing the VM. The attacke...
Identify the affected asset
Confirm whether Erlang OTP, Red Hat OpenStack Platform 16.2, Red Hat OpenStack Platform 17.1 is installed, record the deployed version and installation path, and identify exposed interfaces.
- Record the product name, package or appliance identifier, and installed version.
- Identify internet-facing, administrative, API, and internal access paths.
- Preserve the pre-change configuration and relevant service logs.
Validate the affected-version match
Compare the deployed version with the affected range: >= 6.0, >= 17.0, >= 84adefa331c4159d432d22840663c38f155cd4c1 < 3983d495284331c121f600a80bac9fcf4e16381e, >= 17.0 < 27.3.4.13, >= 28.0 < 28.5.0.2, >= 29.0 < 29.0.2, >= 6.0 < 15.2.7.9, >= 16.0 < 16.4.0.2, >= 17.0 < 17.0.2. Treat incomplete inventory results as unresolved.
Prioritize with independent signals
The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.
Apply supported remediation
Follow the vendor advisory or supported update path. Current fixed-version status: 27.3.4.13, 28.5.0.2, 29.0.2, 15.2.7.9, 16.4.0.2, 17.0.2. Preserve configuration and rollback material before change.
Verify the result
Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.
- Confirm the expected version and package state.
- Run a functional health check for critical service paths.
- Review authentication, error, application, and security monitoring logs.
- Reassess exposure if the supported fix cannot be applied.
Operational boundary
This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.