Critical Security Updates for AlmaLinux 10 and Rocky Linux 10: FreeRDP and cjose Vulnerabilities Fixed in November 2026
Critical security advisories address FreeRDP vulnerabilities in AlmaLinux and Rocky Linux 10 and a cjose encryption flaw in AlmaLinux 10. Explore affected CVEs, security impact, fixed packages, and remediation guidance.
Linux security advisories | November 2026
Critical Security Updates for AlmaLinux 10 and Rocky Linux 10: FreeRDP and cjose Vulnerabilities Fixed in November 2026
SecPod Security Research | November 17, 2026
AlmaLinux issued two Critical security advisories on November 16, 2026, addressing vulnerabilities in FreeRDP and the cjose cryptographic library. Rocky Linux issued a related Critical FreeRDP advisory on November 13. Depending on how these packages are used, the flaws could enable memory corruption, process crashes, potential code execution, or disclosure and forgery of affected encrypted information.
Administrators should identify systems running the relevant packages, determine which vulnerable features are exercised, and validate the fixes using distribution-specific RPM builds. A distribution-wide Critical advisory does not mean every AlmaLinux or Rocky Linux system is directly exploitable.
Advisory snapshot and cross-distribution mapping
FreeRDP
Two distribution advisories • 48 linked CVEs
cjose
One AlmaLinux advisory • 1 linked CVE
The two FreeRDP advisories refer to the same vulnerability group, but their fixed RPM releases differ. The cjose advisory addresses a separate cryptographic weakness.
Advisory status: All three updates are rated Critical by their issuing distributions, and updated RPM packages are available. The distribution-specific fixed builds are listed in the patch availability section below.
What the advisories actually fix
FreeRDP: Protocol processing and memory safety
FreeRDP implements the Remote Desktop Protocol and provides clients, server components, libraries, and WinPR utilities. The AlmaLinux and Rocky Linux advisories describe multiple weaknesses in server redirection, virtual channels, graphics and audio decoding, USB and smartcard handling, authentication, and persistent caches.
These flaws have different prerequisites: some require a client to connect to a malicious RDP server, others require a malicious client to reach an affected FreeRDP server feature, and some require local manipulation of input files. Potential consequences include crashes, information disclosure, memory corruption, keystroke injection, and code execution under applicable conditions. The update also includes bug fixes and a FreeRDP rebase to the 3.32.2 release line.
cjose: Predictable content-encryption key
CVE-2026-53939 affects cjose versions 0.6.1 through 0.6.2.5 when an application creates a JWE using an AES-CBC-HMAC content-encryption algorithm (A128CBC-HS256, A192CBC-HS384, or A256CBC-HS512) with a key-management algorithm that generates a fresh content-encryption key. Instead of a random key, the affected operation uses an all-zero key. The result is ciphertext protected by a publicly predictable key, potentially exposing plaintext and enabling encrypted-content forgery if the JWE is obtained. The AlmaLinux advisory identifies the corresponding distribution security update.
Simply using cjose to parse or consume arbitrary JWE objects is not the vulnerable key-generation operation. Consumers can nevertheless be exposed when they receive or rely on ciphertext produced through the affected encryption path, especially where authenticity is assumed without an independent validation control.
Potential attack paths (illustrative, not observed campaigns)
Path A: FreeRDP memory corruption
Path B: cjose encryption weakness
These simplified flows depict potential mechanisms, not confirmed exploitation. The FreeRDP advisory also includes local-file and other issues not represented by its RDP-input example.
Key CVEs driving the risk
The FreeRDP advisory references for both distributions list 48 CVEs: 33 are explicitly described in the security-fix narrative, while 15 additional identifiers (CVE-2026-121950 through CVE-2026-121964) appear in the advisory reference lists. The cjose advisory lists one CVE. The five entries below are selected representative vulnerabilities, chosen to illustrate cryptographic confidentiality/integrity loss, client-side remote input, server-side virtual-channel processing, and local-file exploitation; they are not the entire set.
| CVE | Weakness | CVSS v3.1 (CNA-reported) | Exploitation conditions | Potential outcome |
|---|---|---|---|---|
| CVE-2026-53939 | cjose all-zero JWE key | 9.1 GitHub, Inc. CNA | Attacker obtains JWE produced with the affected encryption and fresh-key combination | Plaintext recovery or forgery; loss of confidentiality and integrity |
| CVE-2026-91964 | FreeRDP heap overflow in server redirection | 8.8 VulnCheck CNA | FreeRDP client connects to a malicious server; code execution may require a memory-disclosure chain | Client crash or potential code execution |
| CVE-2026-91948 | FreeRDP SHOW_PROTOCOL buffer underwrite | 7.5 VulnCheck CNA | Authenticated malicious client reaches a FreeRDP server using the affected channel option | Server memory corruption and potential code execution |
| CVE-2026-111379 | FreeRDP persistent-cache heap overflow | 7.3 VulnCheck CNA | Local attacker places a crafted cache file that the client subsequently loads | Client crash or potential code execution |
| CVE-2026-111382 | FreeRDP out-of-bounds write during display-frame processing | 8.8 VulnCheck CNA | Client processes crafted frames from a malicious RDP server | Client memory corruption, crash, or potential code execution |
Scoring attribution: These are CVSS v3.1 base scores supplied by the respective CVE Numbering Authorities and displayed in the linked NVD vulnerability records: GitHub, Inc. for the cjose CVE and VulnCheck for the four selected FreeRDP CVEs. They are not represented as scores calculated by NIST/NVD. NVD distinguishes CNA-provided assessments from its own enrichment. The advisories' overall Critical designation does not mean each of the 48 FreeRDP CVEs has an individually Critical score.
The remaining FreeRDP weaknesses span availability (crashes, assertions, uncontrolled allocations, and resource exhaustion); memory safety (out-of-bounds reads/writes, use-after-free, and heap overflow); information disclosure (including uninitialized memory); and protocol or input integrity (including negotiation handling and unexpected input dispatch). For exact prerequisites and impact, consult the individual CVE records linked from the AlmaLinux or Rocky Linux bulletin rather than treating the set as one exploitable flaw.
Real-world exposure and security impact
FreeRDP clients: Workstations, jump servers, administration endpoints, or embedded applications that establish RDP sessions with attacker-controlled or compromised servers could process malicious redirection messages, graphics frames, audio, or other protocol data. A client-side vulnerability requiring connection to a malicious server does not create an automatically exploitable listening service on every installed host.
FreeRDP servers and proxies: An exposed FreeRDP server or proxy can have separate client-originated attack surfaces. For example, the server-side SHOW_PROTOCOL issue requires the relevant feature to be enabled and a malicious authenticated client. Local persistent-cache flaws have yet another prerequisite: a crafted file must be available to the victim process.
Applications creating affected JWE ciphertext with cjose: The primary exposure is in the encryption operation that generates a predictable key. An attacker who obtains JWE ciphertext created through this path may be able to recover the plaintext or forge the encrypted message. Applications that only consume JWE do not trigger this encryption-key flaw merely by parsing messages, although consumers of vulnerable ciphertext can face integrity or confidentiality consequences depending on their trust model. The library's installation, by itself, does not prove that vulnerable JWE data was generated.
Exploitation status and threat context
Research cutoff: November 17, 2026. The AlmaLinux FreeRDP, Rocky Linux FreeRDP, and AlmaLinux cjose advisories establish vulnerability descriptions and available updates, not evidence of an observed attack campaign.
A November 17, 2026 check of the official CISA Known Exploited Vulnerabilities (KEV) catalog (catalog version 2026.11.13) did not identify any of the five representative CVEs in the table above. Their technical descriptions and CNA-reported CVSS data are available through the linked NVD records. This review did not independently establish confirmed in-the-wild exploitation or a reproducible public proof of concept for these five issues. Not appearing in KEV does not prove exploitation has never occurred; revisit the catalog before publication if the research cutoff changes.
There is insufficient campaign-specific evidence here to attribute observed attacker behavior or publish a MITRE ATT&CK tactic chain. Remediation priority should be based on affected installed packages, feature exposure, adversary-controlled input opportunities, and business impact.
Affected releases, fixed builds, and patch availability
| Distribution / advisory | Package family | Fixed build | Verification note |
|---|---|---|---|
| AlmaLinux 10 ALSA-2026:98598 | freerdp, freerdp-libs, freerdp-server, libwinpr and development packages | 2:3.32.2-1.el10_3 | RPM epoch 2: is part of the full EVR; the published RPM filenames show version-release without the epoch. |
| Rocky Linux 10 RLSA-2026:98598 | FreeRDP package family | 2:3.32.2-1.el10_2 | The Rocky Linux advisory explicitly lists the epoch and its distinct el10_2 release. |
| AlmaLinux 10 ALSA-2026:98074 | cjose, cjose-devel | 0.6.2.2-8.el10_3.1 | AlmaLinux's fixed RPM uses a patched vendor release; do not evaluate it using upstream version alone. |
The FreeRDP epoch is material: for RPM comparisons, 2:3.32.2-1.el10_3 and 2:3.32.2-1.el10_2 are distinct vendor update builds, not interchangeable target strings. The AlmaLinux epoch is also reflected in the package changelog metadata, while the Rocky Linux advisory displays it directly. For cjose, upstream fixed the underlying flaw in 0.6.2.6, but AlmaLinux publishes a corrected 0.6.2.2-based RPM release. Detection and patch validation must therefore use the correct distributor's installed package metadata and security errata, not an upstream-only version threshold.
Remediation priorities and verification
The workflow below is intended for impacted assets, not as a blanket instruction to patch hosts where the relevant packages or attack paths are absent.
AlmaLinux 10: FreeRDP or cjose
Rocky Linux 10: FreeRDP only (for these advisories)
Check only the package(s) covered for this OS
Use vendor RPM EVR
Features, input paths, data
Distribution-specific
As required
Validate installed fix
If a decision gate is "No": record the host as outside the advisory's applicable scope or already updated, with evidence; do not label it vulnerable solely because of its distribution.
- Inventory the relevant installations. Identify affected AlmaLinux 10 and Rocky Linux 10 assets with the FreeRDP package family. For AlmaLinux 10, also identify the cjose package and applications depending on its libraries.
- Check the package state and feature exposure. Compare the installed RPM epoch, version, and release with the relevant vendor fix. Review exposed FreeRDP server/proxy features, outgoing client connections, persistent-cache risks, and applications performing AES-CBC-HMAC JWE encryption with cjose.
- Deploy the correct vendor update. Install the applicable distribution-security RPMs from supported repositories. Do not apply AlmaLinux's
el10_3FreeRDP release as the direct version target for Rocky Linux'sel10_2advisory. - Reduce exposure where patching is delayed. Limit untrusted RDP connections, restrict FreeRDP server access to trusted clients, and use the alternatives documented in the cjose CVE record: AES-GCM, a suitable caller-supplied CEK with
alg=dir, or avoiding the affected AES-CBC-HMAC encryption path. These cjose measures only protect new ciphertext. - Address previously generated JWE data. If the vulnerable cjose operation produced sensitive ciphertext, assess exposure, re-encrypt affected data, and rotate secrets that were contained in it. Applying the RPM fix cannot retroactively secure previously generated predictable-key ciphertext.
- Validate closure. Ensure consuming applications and services use updated libraries, restart them as appropriate, reboot only where required, verify the installed vendor build, and perform a follow-up vulnerability assessment.
Instantly Fix Risks in Endpoints & Cloud with Saner
Saner is a continuous and integrated vulnerability & exposure management platform that instantly fixes risks in endpoints and cloud.
Schedule a DemoKey Takeaways
- Prioritize by installed component and attack surface: Critical advisories do not mean every AlmaLinux 10 or Rocky Linux 10 host is exposed.
- Differentiate the fixes: FreeRDP uses
2:3.32.2-1.el10_3for AlmaLinux and2:3.32.2-1.el10_2for Rocky Linux; cjose uses the AlmaLinux-patched0.6.2.2-8.el10_3.1. - Review cjose-generated JWE data: A fixed library protects future encryption, but affected ciphertext may require re-encryption and secret rotation.
- Close the remediation loop: Apply the correct vendor package, restart affected processes when needed, and validate through package checks and rescan results.




