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

Back
New CVE Detected

CVE-2026-12359 – Sensitive Information Disclosure via HTTP Request Smuggling – IBM Security Verify A

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-12359 affects IBM Security Verify Access and IBM Verify Identity Access, including their container editions. The flaw stems from an inconsistent interpretation of HTTP requests between the product’s reverse proxy component (WebSEAL) and backend systems, which could allow a remote attacker to access sensitive information. IBM rates the issue HIGH severity with a CVSS v3.1 base score of 8.1.

Technical details

  • Root cause: The WebSEAL reverse proxy component parses certain HTTP requests differently than the backend application/server it forwards them to, an inconsistency classified as improper authentication (CWE-287).
  • Trigger conditions: An attacker crafts an HTTP request that is interpreted differently by the reverse proxy and the downstream server, enabling request smuggling-style behavior.
  • Attack vector: Network — no authentication or user interaction is required, though the CVSS vector indicates high attack complexity (AC:H).
  • Impact: Successful exploitation could allow a remote, unauthenticated attacker to access sensitive information that should otherwise be restricted; the CVSS vector reflects high confidentiality, integrity, and availability impact.

Affected software

  • IBM Security Verify Access: 10.0 through 10.0.9.2
  • IBM Security Verify Access Container: 10.0 through 10.0.9.2
  • IBM Verify Identity Access: 11.0 through 11.0.3
  • IBM Verify Identity Access Container: 11.0 through 11.0.3

Severity

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

Mitigation and recommended actions

  • Immediate: Apply the IBM-provided fixes — IBM Security Verify Access 10.0.9.2 IF2 and IBM Verify Identity Access 11.0.3 IF1 — available via IBM’s support portal.
  • If patching is delayed: Review IBM’s advisory for any interim configuration guidance on the reverse proxy component, and restrict network exposure of WebSEAL-fronted services to trusted sources until the fix is applied.

How IONIX identifies potentially affected assets

IONIX matches the following signal against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • server response header: WebSEAL/

References

Are you exposed?

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge