Skip to content
VulniPulse
Sign in
Advisory severityMedium5.3Red Hat Linux

Medium [CVE-2026-71468] Cross-user bearer-token reuse via global federation-config cache

This medium-severity Red Hat Linux advisory covers CVE-2026-71468 affecting Red Hat Advanced Cluster Management for Kubernetes 2.11, Red Hat Advanced Cluster Management for Kubernetes 2.13, Red Hat Advanced Cluster Management for Kubernetes 2.14.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-71468 Source published Source updated

VulniPulse record published Record updated

CVE-2026-71468
Affected products & platforms
Red Hat LinuxUnclassified
Open source advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery
Get CVE alertsSee app features

Summary

A flaw was found in acm-search-v2-api-rhel9. When the `getFederationConfig` function refreshes its cache, it improperly reuses a user's bearer token for all subsequent federated requests until the cache expires.

This allows other authenticated users to gain unauthorized access to remote managed hub search results, leading to information disclosure. This Moderate impact flaw in Red Hat Advanced Cluster Management for Kubernetes allows for cross-user data access to remote managed hub search results.

The vulnerability arises from the reuse of a bearer token across different user requests due to a shared cache. Exploitation requires the `FEATURE_FEDERATED_SEARCH` to be enabled, which is off by default and typically only configured in Global Hub deployments.

Red Hat severity: Moderate — CVSS 5.3 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N). Weakness: CWE-266.

Red Hat fixing advisory: RHSA-2026:60387, RHSA-2026:60390, RHSA-2026:60388, RHSA-2026:60389, RHSA-2026:60391, RHSA-2026:60386.

Affected products named by the advisory: Red Hat Advanced Cluster Management for Kubernetes 2.11; Red Hat Advanced Cluster Management for Kubernetes 2.13; Red Hat Advanced Cluster Management for Kubernetes 2.14; Red Hat Advanced Cluster Management for Kubernetes 2.15; and 2 more.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.

Official advisory · high-confidence parse· fetched 2 days ago·verify at source

Fixed versions
  • rhacm2/acm-search-v2-api-rhel9:1787689524
  • rhacm2/acm-search-v2-api-rhel9:1787263804
  • rhacm2/acm-search-v2-api-rhel9:1786723845
  • rhacm2/acm-search-v2-api-rhel9:1787238618
  • rhacm2/acm-search-v2-api-rhel9:1787191668
  • rhacm2/acm-search-v2-api-rhel9:1787229541
  • RHSA-2026:60387
  • RHSA-2026:60390
  • RHSA-2026:60388
  • RHSA-2026:60389
  • RHSA-2026:60391
  • RHSA-2026:60386

Official advisory · high-confidence parse· fetched 2 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • To mitigate this issue, ensure that the `FEATURE_FEDERATED_SEARCH` is not enabled if federated search functionality is not required. This feature is disabled by default in Red Hat Advanced Cluster Management for Kubernetes. If `FEATURE_FEDERATED_SEARCH` is enabled, consider disabling it to prevent unauthorized cross-user data access. Disabling this feature will impact the ability to perform federated searches across managed hubs.

Official advisory · high-confidence parse· fetched 2 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.