Red Hat FreeRDP Update Fixes Critical CVE-2026-91949 on RHEL 10

P1 — VALIDATE AND UPDATECritical · 9.3 (official CVSS v3.1)EXPLOITATION: NOT STATED

Quick Answer

The authority published RHSA-2026:73979 for FreeRDP on RHEL 10.2. Red Hat corrected a Critical FreeRDP vulnerability in the RHEL 10.2 package stream. Affected deployments should be matched to the authority's exact scope and moved to the supported fixed release.

Confirm Scope And Apply The Supported Fix

What to do now: Inventory FreeRDP on RHEL 10.2, match the exact affected release or feature, apply the authority-supported fixed build or service remediation, validate the dependent workflow, and preserve evidence.

Open the authoritative advisory

Last verified: 2026-10-02 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeFreeRDP on RHEL 10.2
AdvisoryRHSA-2026:73979
CVECVE-2026-91949
Authoritative release date2026-10-02 14:18:22 UTC
Authority revision date2026-10-02 14:18:47 UTC
Affected versionsRHEL 10.2 FreeRDP packages before 3.10.3-12.el10_2.13.
Fixed versionfreerdp 3.10.3-12.el10_2.13
CVSS base score9.3 (official CVSS v3.1)
CVSS severityCritical
Exploitation statusNot stated by the authority; no exploitation claim is inferred.

What Changed

Red Hat corrected a Critical FreeRDP vulnerability in the RHEL 10.2 package stream.

What To Validate Now

  1. Inventory. Locate FreeRDP on RHEL 10.2 deployments, versions, enabled features, exposure paths, owners, and dependent services.
  2. Establish applicability. Match entitlement, product stream, architecture, source package or image repository, and each advisory's product status. Do not apply one branch's build or digest to another branch.
  3. Remediate. Use the supported Red Hat channel to deploy freerdp 3.10.3-12.el10_2.13. For container images, pin and verify the exact signed digest listed for the matching architecture.
  4. Validate. Confirm the installed package build, active live patch, or running image digest; restart or redeploy affected workloads where required; validate application and recovery workflows; and record exceptions.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Confirm entitlement and branch support, test package or image compatibility, preserve prior packages or image digests and rollback evidence, and do not infer exploitation from severity.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.