Red Hat Updates curl and libcurl on RHEL 9.8 EUS
Quick Answer
Red Hat published RHSA-2026:80511 for curl and libcurl on RHEL 9.8 Extended Update Support. Apply curl and libcurl 7.76.1-40.el9_8.8 only to the matching entitled branch, validate dependent services, and retain package and change evidence.
Confirm Scope And Apply The Supported Remediation
What to do now: Inventory curl and libcurl on RHEL 9.8 Extended Update Support, compare installed NEVRAs with the exact advisory relationships, deploy curl and libcurl 7.76.1-40.el9_8.8 from the supported channel, restart dependent services where required, and validate representative operations.
Last verified: 2026-10-12 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | curl and libcurl on RHEL 9.8 Extended Update Support |
|---|---|
| Advisory | RHSA-2026:80511 |
| CVEs | CVE-2026-11856, CVE-2026-8924 |
| Authoritative release date | 2026-10-12 04:27:33 UTC |
| Authority revision date | 2026-10-12 14:16:40 UTC |
| Affected versions | The entitled RHEL 9.8 EUS curl and libcurl package relationships listed by RHSA-2026:80511. |
| Fixed version | curl and libcurl 7.76.1-40.el9_8.8 |
| CVSS base score | 6.5 (CVSS v3.1) |
| CVSS severity | Medium |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
Red Hat supplied supported packages for URL parsing and connection-reuse flaws involving trailing-dot hostnames and reused handles across origins.
What To Validate Now
- Inventory. Locate curl and libcurl on RHEL 9.8 Extended Update Support deployments, versions, enabled features, exposure paths, owners, and dependent services.
- Establish applicability. Compare each deployment with the authority's affected-version statement: The entitled RHEL 9.8 EUS curl and libcurl package relationships listed by RHSA-2026:80511. Do not infer applicability from product family or severity alone.
- Remediate. Apply curl and libcurl 7.76.1-40.el9_8.8 through the supported vendor or project channel, following the current advisory and change-control requirements.
- Validate. Confirm the resulting version or managed-service state, exercise representative functionality and recovery paths, monitor for regressions, and document exceptions.
- 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
Do not substitute package builds across RHEL branches. Test curl and libcurl consumers, integrations, service restarts, and rollback before broad deployment. Preserve the authority snapshot, asset and owner records, before-and-after versions, change approval, installation output, validation results, exceptions, and rollback evidence.
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.

