Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-71468 medium CVSS 5.3

Vulnerability in acm-search-v2-api-rhel9 (CVE-2026-71468)

Summary

Vulnerability in acm-search-v2-api-rhel9 (CVE-2026-71468). Confidential information can be exposed externally. Exploitable via getFederationConfig.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-71468 has been found in acm-search-v2-api-rhel9.
Attackers can target a specific entry point like getFederationConfig over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "acm-search-v2-api-rhel9 CVE-2026-71468" on the vendor's site.

CVE-2026-71468 (acm-search-v2-api-rhel9) — CWE-266 / CVSS v3 5.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: getFederationConfig
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-266) exists in acm-search-v2-api-rhel9. Attackers reach the vulnerable code path via getFederationConfig.

📍 Affected scope

Check the vendor advisory for the affected versions of acm-search-v2-api-rhel9. Attack surface: getFederationConfig.

🔥 Severity

Severity: Medium (CVSS 5.3/10). Confidential information can be exposed externally.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'acm-search-v2-api-rhel9' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'acm-search-v2-api-rhel9' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で acm-search-v2-api-rhel9 を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details