Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-17635 – Authentication Bypass / Unauthorized Actions – IBM FTM for Red Hat OpenShift 4.0.6.

Be the first to know when new zero-days emerge:

Summary

CVE-2026-17635 is a missing authentication vulnerability (CWE-306) affecting IBM Financial Transaction Manager (FTM) for Red Hat OpenShift. Due to improper configuration of HTTP method-based security constraints, a remote, unauthenticated attacker can perform unauthorized actions against the application. The flaw carries a Critical CVSS v3.1 base score of 9.1 and requires no privileges or user interaction to exploit.

Technical details

  • Root cause: The application’s security constraints enforce authentication only for specific HTTP methods (e.g., GET/POST), leaving other HTTP methods (e.g., PUT, DELETE, or alternate verbs) improperly protected on the same URL paths.
  • Trigger conditions: An attacker sends requests using an HTTP method that falls outside the configured security constraint, bypassing the intended access control checks for that endpoint.
  • Attack vector: Network — the vulnerable endpoints are reachable remotely and do not require any prior authentication (PR:N) or user interaction (UI:N).
  • Impact: Successful exploitation allows an unauthenticated attacker to perform unauthorized actions, resulting in high impact to confidentiality and integrity (data exposure and unauthorized modification); availability is not directly impacted per the CVSS vector.

Affected software

  • IBM Financial Transaction Manager (FTM) for Red Hat OpenShift, versions 4.0.6.0 through 4.0.10.0, Interim Fix 064

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: Upgrade IBM Financial Transaction Manager (FTM) for Red Hat OpenShift to version 4.0.11.0 or later, which resolves this issue.
  • If unable to patch immediately: IBM has not published a workaround for this specific issue; organizations should restrict network access to FTM management/application endpoints to trusted networks only and monitor for unexpected HTTP methods (e.g., PUT, DELETE, TRACE) directed at application endpoints until the patch can be applied.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge