RHSA-2026:36651HighCVSS 9.1

Red Hat Security Advisory: Red Hat Edge Manager Version 1.0.3 Security Update

Published
July 8, 2026
Last Modified
August 26, 2026

🔗 CVE IDs covered (25)

CVE-2026-4926 →CVE-2026-29063 →CVE-2026-32141 →CVE-2026-32280 →CVE-2026-33186 →CVE-2026-33810 →CVE-2026-33811 →CVE-2026-39828 →CVE-2025-61729 →CVE-2025-68121 →CVE-2025-69873 →CVE-2026-6322 →CVE-2026-39829 →CVE-2026-39830 →CVE-2026-39832 →CVE-2026-39835 →CVE-2026-22029 →CVE-2026-25679 →CVE-2026-42154 →CVE-2025-13465 →CVE-2026-4800 →CVE-2026-39821 →CVE-2026-42151 →CVE-2026-42508 →CVE-2026-46595 →

📋 Description

CVE-2025-13465 — lodash: prototype pollution in _.unset and _.omit functions CVE-2025-61729 — crypto/x509: golang: Denial of Service due to excessive resource consumption via crafted certificate CVE-2025-68121 — crypto/tls: crypto/tls: Incorrect certificate validation during TLS session resumption CVE-2025-69873 — ajv: ReDoS via $data reference CVE-2026-4800 — lodash: lodash: Arbitrary code execution via untrusted input in template imports CVE-2026-4926 — path-to-regexp: path-to-regexp: Denial of Service via crafted regular expressions CVE-2026-6322 — fast-uri: fast-uri: URI authority bypass due to improper delimiter handling CVE-2026-22029 — @remix-run/router: react-router: React Router vulnerable to XSS via Open Redirects CVE-2026-25679 — net/url: Incorrect parsing of IPv6 host literals in net/url CVE-2026-29063 — immutable-js: Immutable.js: Arbitrary code execution via Prototype Pollution CVE-2026-32141 — flatted: flatted: Unbounded recursion DoS in parse() revive phase CVE-2026-32280 — crypto/x509: crypto/tls: golang: Go: Denial of Service vulnerability in certificate chain building CVE-2026-33186 — google.golang.org/grpc/grpc-go: google.golang.org/grpc/authz: gRPC-Go: Authorization bypass due to improper HTTP/2 path validation CVE-2026-33810 — crypto/x509: golang: Go crypto/x509: Certificate validation bypass due to incorrect DNS constraint application CVE-2026-33811 — net: golang: Go net package: Denial of Service via long CNAME response in LookupCNAME CVE-2026-39821 — golang.org/x/net/idna: golang: net/http: golang.org/x/net/idna: Privilege escalation via incorrect Punycode label processing CVE-2026-39828 — golang.org/x/crypto/ssh: golang.org/x/crypto/ssh: Unauthorized command execution via discarded SSH permissions CVE-2026-39829 — golang.org/x/crypto/ssh: golang.org/x/crypto/ssh: Denial of Service via crafted public key with excessive parameters CVE-2026-39830 — golang.org/x/crypto/ssh: golang.org/x/crypto/ssh: Denial of Service via resource leak from unsolicited SSH responses CVE-2026-39832 — golang.org/x/crypto/ssh/agent: golang.org/x/crypto/ssh/agent: Security bypass due to improper handling of key restrictions CVE-2026-39835 — golang.org/x/crypto/ssh: golang: golang.org/x/crypto/ssh: Denial of Service via crafted SSH certificate CVE-2026-42151 — github.com/prometheus/prometheus: Prometheus: Information disclosure of Azure OAuth client secret via config API CVE-2026-42154 — github.com/prometheus/prometheus: Prometheus: Denial of Service via uncontrolled memory allocation in remote read endpoint CVE-2026-42508 — golang.org/x/crypto/ssh/knownhosts: golang: golang.org/x/crypto/ssh/knownhosts: Revocation bypass via unchecked SignatureKey CVE-2026-46595 — golang.org/x/crypto/ssh: golang.org/x/crypto/ssh: Authorization bypass due to skipped source-address validation

🎯 Affected products25

  • Red Hat Edge Manager 1.0
  • registry.redhat.io/rhem/flightctl-alert-exporter-rhel9@sha256:7e7958da7226d0bb3b19bc1447e8545d7d96988d0bde589fbdd649e011586a95_amd64 as a component of Red Hat Edge Manager 1.0
  • registry.redhat.io/rhem/flightctl-alert-exporter-rhel9@sha256:bb489e9db92d4fb9715575d079cb8ac8500efc1a53b232c08891ef0c1352a8e7_arm64 as a component of Red Hat Edge Manager 1.0
  • registry.redhat.io/rhem/flightctl-alertmanager-proxy-rhel9@sha256:9280560b3774698fbd30a1e3a14e6b57f42609bc24bbe8b025a629450b0a7927_amd64 as a component of Red Hat Edge Manager 1.0
  • registry.redhat.io/rhem/flightctl-alertmanager-proxy-rhel9@sha256:e4c9707494658435871f50c35a690d8cc4d01bf1325dc6ca9379cd40a302644a_arm64 as a component of Red Hat Edge Manager 1.0
  • registry.redhat.io/rhem/flightctl-api-rhel9@sha256:5f754d14e660f29e18748a47cf56e3c18f656472cd93b6aff939b998f058f89d_amd64 as a component of Red Hat Edge Manager 1.0
  • registry.redhat.io/rhem/flightctl-api-rhel9@sha256:fb4fb7684ce126b8469959ed878b3a7a91884c356c9f6bfac99bd4b2f23ce6a2_arm64 as a component of Red Hat Edge Manager 1.0
  • registry.redhat.io/rhem/flightctl-cli-artifacts-rhel9@sha256:3a7cfaa9f3b0900827022d18f529f211361e6ba372eb8458035c4e4f0e3ae607_amd64 as a component of Red Hat Edge Manager 1.0
  • registry.redhat.io/rhem/flightctl-cli-artifacts-rhel9@sha256:c9aa3e4437c767e9a08731b395626b8d69ba466c7f0f1eb6245b9c19ce83e908_arm64 as a component of Red Hat Edge Manager 1.0
  • registry.redhat.io/rhem/flightctl-db-setup-rhel9@sha256:0b775738a61fe65ffbe59629fe7451eb02b1cf1c40740e5c30a33f0ff0eede2d_amd64 as a component of Red Hat Edge Manager 1.0
  • registry.redhat.io/rhem/flightctl-db-setup-rhel9@sha256:84f67cafc98159f1308a6e35dbd4290e7cc2d946d078e98e3900d78e3eb3ccf7_arm64 as a component of Red Hat Edge Manager 1.0
  • registry.redhat.io/rhem/flightctl-pam-issuer-rhel9@sha256:225a7daaaaf072c45225ae3f4ee793c48dd82f62334d8213872b3b022c30d44e_arm64 as a component of Red Hat Edge Manager 1.0
  • registry.redhat.io/rhem/flightctl-pam-issuer-rhel9@sha256:6d9c18658ff3931e918eab69039751b48922c77b8c47605a6ce240bce9982568_amd64 as a component of Red Hat Edge Manager 1.0
  • registry.redhat.io/rhem/flightctl-periodic-rhel9@sha256:0ee30ee155ff08f2a637ad7a51cb05c587761ba91ad0c261df2100b622ba509b_arm64 as a component of Red Hat Edge Manager 1.0
  • registry.redhat.io/rhem/flightctl-periodic-rhel9@sha256:b0c0550b7f3d58517cb14220f5735694ac0a581335d0197645bdcb5ad4011a81_amd64 as a component of Red Hat Edge Manager 1.0
  • registry.redhat.io/rhem/flightctl-telemetry-gateway-rhel9@sha256:51ddafb4b356eb322c05191e18b9e7e8734eb90fefc9e79f3f50310fcefc1d7f_amd64 as a component of Red Hat Edge Manager 1.0
  • registry.redhat.io/rhem/flightctl-telemetry-gateway-rhel9@sha256:aba941ba3f928360a744e26745f34962f6ecf3d211b37d4b50bee68803c370ca_arm64 as a component of Red Hat Edge Manager 1.0
  • registry.redhat.io/rhem/flightctl-ui-ocp-rhel9@sha256:5f14b823c53919e94d6b57a5a681008a6bc0ba6ee3fd74e744c792c6df11baad_amd64 as a component of Red Hat Edge Manager 1.0
  • registry.redhat.io/rhem/flightctl-ui-ocp-rhel9@sha256:e8480249816c12331f27b87d9edb1b15fb8efb8cc8b86bda38750cde3e05a60e_arm64 as a component of Red Hat Edge Manager 1.0
  • registry.redhat.io/rhem/flightctl-ui-rhel9@sha256:e75051d27fae381533a2fb8e8a5dd3e68700dbfea20c50f4d580705bed6e5cf8_arm64 as a component of Red Hat Edge Manager 1.0
  • registry.redhat.io/rhem/flightctl-ui-rhel9@sha256:f1e785adb22e3d3c869eabe31f5009f8f8a928e4ad9b553a4bf254476e233e70_amd64 as a component of Red Hat Edge Manager 1.0
  • registry.redhat.io/rhem/flightctl-userinfo-proxy-rhel9@sha256:636c2b9fe1b410168f9f5b8956255ef0eb6b0fd2b9247fb020ec9b50df5e5321_arm64 as a component of Red Hat Edge Manager 1.0
  • registry.redhat.io/rhem/flightctl-userinfo-proxy-rhel9@sha256:ceb10edf040f4d60df9307758ff49f212bf950f93db6ae04d92d686d372ba8bb_amd64 as a component of Red Hat Edge Manager 1.0
  • registry.redhat.io/rhem/flightctl-worker-rhel9@sha256:11bd15489ac98c413d610197422b504fa0fb4478f2d838b91de35e3b9380de79_amd64 as a component of Red Hat Edge Manager 1.0
  • registry.redhat.io/rhem/flightctl-worker-rhel9@sha256:4ae2d884d5b5d7caf876bbb2118b715ae632e5c4dad3d19edd15ec935e588395_arm64 as a component of Red Hat Edge Manager 1.0

✅ Remediation

See the following documentation for details on how to enable Red Hat Edge Manager and more: https://docs.redhat.com/en/documentation/red_hat_edge_manager/1.0 Workaround: To mitigate this issue, implement strict input validation before passing any property paths to the _.unset and _.omit functions to block attempts to access the prototype chain. Ensure that strings like __proto__, constructor and prototype are blocked, for example. Workaround: To mitigate this issue, disable the $data feature if your application does not require it. If $data must be used, implement strict validation of the input fields that are referenced by the pattern keyword to ensure they contain only expected and safe characters. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. Workaround: To mitigate this vulnerability, limit the use of multiple sequential optional groups in route patterns within applications that use `path-to-regexp`. Additionally, avoid directly passing user-controlled input as route patterns to prevent the generation of maliciously crafted regular expressions. Workaround: To mitigate this issue, implement infrastructure-level normalization to ensure all incoming HTTP/2 `:path` headers are properly formatted with a leading slash before reaching the gRPC-Go server. This can be achieved by configuring a reverse proxy or API gateway to validate and normalize the `:path` header. Ensure that any such intermediary is properly configured and restarted to apply the changes, which may temporarily impact service availability. Workaround: To mitigate this issue, applications can be configured to use the pure Go DNS resolver instead of the `cgo` DNS resolver. This can be achieved by setting the `GODEBUG` environment variable to `netdns=go`. For example, to run a Go application with this mitigation: `GODEBUG=netdns=go /path/to/your/go/application`. This change may require restarting affected applications or services to take effect. Users should verify that this change does not negatively impact DNS resolution for their specific application environment. Workaround: Upgrade to a fixed golang.org/x/net release that includes the idna correction, via updated golang or dependent package rebuilds. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. Workaround: To mitigate this denial of service vulnerability, restrict network access to any service that utilizes the `golang.org/x/crypto/ssh` library and is exposed to untrusted networks. Implement firewall rules to allow connections only from trusted hosts or networks. This action limits the ability of malicious peers to send unsolicited global request responses. A restart of the affected service may be necessary for the new network rules to be applied effectively. Workaround: To mitigate this issue, restrict network access to the Prometheus remote read endpoint (/api/v1/read). Configure firewall rules or network policies to permit connections only from trusted internal networks or authorized clients. This action reduces the attack surface by limiting exposure to unauthenticated remote attackers. A service restart or reload may be required for the changes to take effect.

🔗 References (30)