CVE-2026-32146 remediation guide
Gleam Gleam, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 7
Improper path validation vulnerability in the Gleam compiler's handling of git dependencies allows arbitrary file system modification during dependency download. Dependency names from gleam.toml and manifest.toml are incorporated into filesystem paths without sufficient validation or confinement to the intended dependency directory, allowing attacker-controlled paths (via relative traversal such as ../ or absolute paths) to target filesystem locations outside that directory. When resolving git dependencies (e.g. via gleam deps download), the computed path is used for filesystem operations i...
Identify the affected asset
Confirm whether Gleam Gleam, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 7 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: >= 1.9.0-rc1, >= a4fde22445ab8e5cc79c2ff48971616cb570702c, >= v1.9.0-rc1-elixir < v1.15.4-elixir, >= v1.9.0-rc1-erlang < v1.15.4-erlang, >= v1.9.0-rc1-node < v1.15.4-node, >= v1.9.0-rc1-node-slim < v1.15.4-node-slim, >= v1.9.0-rc1-elixir-slim < v1.15.4-elixir-slim, >= v1.9.0-rc1-erlang-slim < v1.15.4-erlang-slim, >= v1.9.0-rc1-erlang-alpine < v1.15.4-erlang-alpine, >= v1.9.0-rc1-elixir-alpine < v1.15.4-elixir-alpine, >= v1.9.0-rc1-node-alpine < v1.15.4-node-alpine, >= v1.9.0-rc1-scratch < v1.15.4-scratch, >= 1.9.0 < 1.15.4. 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: 1.15.4. 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.