IBM
Monthly
Arbitrary code execution in IBM Cyber Fraud 1.0.0 through 1.0.2 requires an authenticated low-privilege user to upload a file with a dangerous type and then depends on a victim interacting with that file; the upload handler does not restrict dangerous file types (CWE-434). The vendor CVSS score is 6.8, while the independent assessment rates confidentiality, integrity, and availability impact as high with scope unchanged; the mandatory authentication (PR:L) and user interaction (UI:R) limit anonymous, fully automated exploitation. No public exploit code or CISA KEV entry was identified at time of analysis, and the realistic risk is moderate and context-dependent rather than an emergency.
Server-side request forgery in IBM ContextForge MCP Gateway 0.1.0 through 1.0.5 lets users who hold an authenticated account with gateway-creation privileges direct arbitrary HTTP POST requests at internal network services, localhost-bound daemons, and cloud metadata endpoints (AWS IMDSv1, GCP, Azure). The flaw is reachable only through the OAuth client-credentials gateway registration flow, where the oauth_config.token_url parameter is used without the SSRF validation that already guards the gateway.url field; the gateway then immediately POSTs form-encoded client credentials to the attacker-named URL and, when the reply fails OAuth token parsing, reflects up to 256 characters of the response body in an HTTP 502 error. Exploitation requires valid low-privileged credentials (PR:L) and returns only limited/blind data, no public exploit code was identified at time of analysis, there is no CISA KEV listing, and EPSS is 0.18% (7th percentile) - a moderate, low-priority issue rather than an emergency.
Denial of service in IBM Storage TS4500 Library and IBM Diamondback Tape Library firmware versions 1.1.1.6 through 1.12.0.3 allows an authenticated low-privilege user to exhaust system resources by sending specially crafted SMTP requests to the library's email/notification management interface. The issue is a moderate, not top-tier, priority because authentication is mandatory, impact is limited to availability, and the appliance is typically internal rather than internet-exposed; no public exploit was identified at time of analysis. A vendor patch is available per IBM advisory node/7292612.
IBM Storage TS4500 Library versions 1.1.1.6 through 1.12.0.3 fail to invalidate a session after logout, allowing an authenticated user who obtains or retains a still-valid session identifier to impersonate another user. Exploitation requires a second user to have logged out and the attacker to possess that session token, so impact is limited to multi-user or insider scenarios and the issue is moderate severity/low urgency. Patch is available per IBM advisory node/7292613; no public exploit identified at time of analysis.
IBM TS4500 Library firmware 1.1.1.6 through 1.12.0.3 fails to invalidate sessions, allowing an authenticated attacker who retains a usable session identifier to impersonate another user on the library management interface. CVSS 3.1 scores this 6.3 with vector AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L, meaning exploitation requires an authenticated session and is bounded to limited confidentiality, integrity, and availability impact. No public exploit identified at time of analysis, and IBM has published a vendor patch advisory.
A race condition in IBM Storage TS4500 Library firmware versions 1.1.1.6 through 1.12.0.3 lets a remote, low-privileged authenticated user escalate to administrative privileges by timing an operation against a concurrent privileged action. The flaw is a privilege-escalation issue rather than a pre-authentication bypass, since valid credentials for the library management interface are mandatory, and successful exploitation depends on winning a non-deterministic race that may require repeated attempts. IBM has released a fix; no public exploit code or confirmed active exploitation was identified at time of analysis, and the EPSS-style risk profile places this as a patch-on-a-normal-cycle item.
IBM Cloud Pak System 2.3.6.0 and 2.3.6.1 employ weaker-than-expected cryptographic algorithms, allowing an attacker who obtains the protected ciphertext to decrypt highly sensitive information. The CVSS 5.9 score (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N) reflects that exploitation requires capturing the encrypted data and performing cryptanalysis, which substantially constrains real-world risk despite the unauthenticated network vector. No public exploit code or active exploitation has been identified at time of analysis, and IBM has released a vendor patch.
HTML injection (CWE-80) in IBM Cloud Pak System 2.3.6.0 and 2.3.6.1 lets a remote attacker who already holds valid credentials on the web interface inject malicious HTML/script that executes in another user's browser within the hosting site's security context. Impact is limited to low confidentiality and integrity effects (CVSS 5.4) and requires both a legitimate authenticated account and a victim subsequently viewing the injected content, so it is a routine patch-management item rather than an urgent one. No public exploit code or confirmed active exploitation was identified in the available data; the vendor has published a fix advisory.
Improper certificate validation in IBM Concert 1.0 through 3.0.0 allows an attacker who already holds a man-in-the-middle position to present forged or invalid TLS certificates that the product may accept, yielding low confidentiality and integrity impact with no availability effect. The provided CVSS 3.7 vector requires high attack complexity and user interaction, and the supplied vectors conflict on whether low-level privileges (PR:L) are required, so authentication requirements are not consistently confirmed from the available data; no public exploit code or CISA KEV entry was identified at time of analysis. This is a low-severity issue and the signals are consistent in pointing to limited real-world risk.
Information disclosure in IBM Concert 1.0 through 3.0.0 can expose sensitive heap-resident data to an authenticated local attacker with low privileges who is able to inspect the application's process memory, with high attack complexity and no public exploit identified at time of analysis. The flaw is CWE-244 (failure to clear heap memory before release), rated CVSS 4.7, and a vendor patch is available. Realistic risk is limited to post-compromise or insider scenarios on hosts where an attacker already has local access.
Cross-origin resource sharing (CORS) misconfiguration in IBM Concert 1.0 through 3.0.0 can allow attacker-controlled web content to carry out privileged actions in the context of a victim's authenticated session when the allowed domain is not limited to trusted domains. The vendor rates attack complexity High and impact limited, and the CVSS vector indicates no prior privileges are required (PR:N) even though practical exploitation depends on a victim with an active Concert session loading malicious web content. IBM has released a fix; no public exploit was identified at time of analysis.
Information disclosure in IBM Concert 1.0 through 3.0.0 exposes schema suggestion data to network-reachable attackers; the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) indicates no authentication or user interaction is required, although the impact is limited to low confidentiality loss with no integrity or availability effect. The flaw is rated 5.3 (moderate) and is chiefly useful for reconnaissance rather than direct compromise. No public exploit code or CISA KEV entry was identified at time of analysis, and patch availability is documented in the vendor advisory.
IBM Concert versions 1.0 through 3.0.0 persist web page content to a local on-disk cache that is not adequately protected, so a second user with an account on the same host can read cached page data belonging to another Concert user. The issue is strictly local (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, base score 4.0) and impacts confidentiality only - there is no network attack path, no integrity or availability effect, and single-user or isolated deployments where no other principal can reach the cache are not meaningfully exposed. Exploitation requires an attacker to already hold local/interactive access to the host; no public exploit code has been identified at time of analysis and the issue is not in CISA KEV. A vendor patch is available.
IBM Concert 1.0 through 3.0.0 can expose highly sensitive information because it relies on weaker-than-expected cryptographic algorithms, allowing an attacker who obtains the protected data to attempt to recover plaintext. The CVSS vector (AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N) describes a network-reachable, unauthenticated and no-interaction path, but exploitation is high-complexity and limited to confidentiality impact. No CISA KEV entry and no public exploit were identified at time of analysis, so this is a low-priority cryptography hardening issue rather than an actively exploited intrusion vector.
Log injection in IBM Concert 1.0 through 3.0.0 lets remote unauthenticated attackers corrupt or forge log records by supplying input containing special or control characters that the product writes to its log files without neutralization. The CVSS 3.1 score is 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N), so the only assessed impact is limited integrity damage to log data - there is no code execution, data disclosure, or availability loss. No public exploit code or confirmed active exploitation was identified at time of analysis, and real-world severity depends on how downstream log consumers (viewers, SIEM parsers, audit reviews) handle unescaped content.
Cross-site scripting in the IBM Concert Web UI (versions 1.0 through 3.0.0) lets remote attackers inject arbitrary JavaScript into pages viewed by other users, potentially disclosing credentials from within a trusted session. Exploitation requires the victim to interact with attacker-supplied content - such as clicking a crafted link or loading a page reflecting the payload - while authenticated to Concert, so practical risk is targeted rather than mass exploitation. No public exploit code or confirmed active exploitation is known, and IBM has released a vendor fix; EPSS context is not provided in the available data.
Crafted messages published into IBM MQ 9.4.5.0 or 9.4.5.1 can crash the applications that consume them, giving an authenticated message producer a denial-of-service primitive against queue-processing services. Successful exploitation requires a valid MQ identity with put authority on a queue that a vulnerable consumer reads; the CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, score 6.5) confirms the attacker must be authenticated and that only availability is impacted, with no confidentiality or integrity effect. There is no CISA KEV listing and no public exploit identified at time of analysis, so this should be handled as routine, medium-severity patch management rather than emergency response, especially since deployments outside the 9.4.5.0-9.4.5.1 range are not affected.
Denial of service in IBM MQ client applications that consume messages asynchronously can be triggered when a queue name carrying an improperly validated length value reaches the client, producing a buffer overflow (CWE-120) that crashes or hangs the consuming application. The flaw affects IBM MQ Operator and IBM MQ Advanced Container Images deployments and is reachable either by an attacker who already controls the queue manager or by a man-in-the-middle able to tamper with message metadata on unencrypted, non-TLS channels. IBM has released a vendor patch per its support advisory, no public exploit code or active exploitation has been identified at time of analysis, and the CVSS 5.9 score reflects availability-only impact with high attack complexity.
Denial of service in IBM MQ Operator and IBM MQ Advanced container images lets an authenticated MQ client crash the queue manager by sending an MQOPEN request whose offset values are not properly validated, producing a buffer-handling fault in the queue manager process. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) shows the limiting factor is credentials: the attacker must already hold a valid MQ identity and an established connection able to issue MQ API calls, so exposure is limited to insiders or attackers who have compromised an MQ application identity. Confidentiality and integrity are unaffected, the vendor has published a fix, and no public exploit code or active exploitation has been identified at time of analysis (CISA SSVC exploitation: none, automatable: no).
Authenticated IBM MQ clients can cause a bounded denial of service and obtain limited information about process memory layout in IBM MQ Operator and IBM MQ Advanced Container Images deployments by sending a specially crafted request that triggers an out-of-bounds read. The issue requires a valid MQ client session and network access to the queue manager listener, and impact is limited to availability and low-confidentiality disclosure rather than code execution or data modification. No public exploit was identified at time of analysis, and IBM has published a vendor patch.
Authenticated denial of service in IBM MQ container deployments - specifically the MQ Operator and MQ Advanced container images - lets a remote user who already holds valid MQ credentials crash the queue manager by sending specially crafted multicast status messages that drive the process into a NULL pointer dereference. Impact is availability-only (CVSS 6.5, A:H with C:N/I:N); confidentiality and integrity are unaffected. Exploitation is further constrained because the target deployment must have multicast messaging configured and enabled, a non-default capability absent from most standard queue-manager installations, and no public exploit has been identified at time of analysis.
Authenticated users of IBM MQ Operator and IBM MQ Advanced container image deployments can cause a denial of service against the queue manager by submitting malformed RFH2 message header fields through queued publish/subscribe operations. The flaw is rated CVSS 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), reflecting high availability impact only - there is no disclosure or modification of message data - and requires valid MQ credentials with authorization to publish or subscribe, so anonymous remote parties are not positioned to exploit it. No public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor has published remediation guidance; the practical exposure is limited to environments that both grant the attacker a usable principal and expose queued pub/sub messaging.
Denial of service in IBM MQ Operator and MQ Advanced Container Images allows an authenticated MQ client to crash the queue manager agent by sending a crafted asynchronous consume request that triggers untrusted deserialization (CWE-502). The CVSS 6.5 vector confirms network reachability, low privileges (PR:L), no user interaction, and availability-only impact; confidentiality and integrity are unaffected, and this is a moderate-priority availability issue rather than a top-tier emergency. No public exploit was identified at time of analysis, CISA SSVC rates exploitation as none and automatable as no, and IBM has published a vendor patch.
Path traversal in IBM MQ Web Console allows an authenticated administrator to write files outside the intended directory in deployments using IBM MQ Operator or IBM MQ Advanced Container Images. The issue is low severity (CVSS 2.7) with integrity-only impact and a high privilege prerequisite, and no public exploit identified at time of analysis; a vendor patch is available per IBM advisory.
Malformed compressed message data delivered to containerized IBM MQ deployments (MQ Operator and MQ Advanced Container Images) can drive a minor out-of-bounds read (CWE-125) in the decompression code path, but the broker rejects the malformed request and does not return the over-read bytes, so no message or memory contents are exposed. The attacker must already hold valid MQ connection credentials (CVSS PR:L) and clear high attack complexity (AC:H) by crafting a specific malformed compressed structure, keeping the issue at CVSS 3.1 (Low). No public exploit code or active exploitation has been identified at time of analysis, and IBM has published a vendor fix via its support portal.
Authenticated IBM MQ users holding valid queue-manager credentials can trigger an off-by-one buffer overflow by submitting a specially crafted object name, causing process instability or a crash of MQ components. The impact is availability-only (CVSS 4.3, PR:L, A:L) with no path to data disclosure or code execution, and the CPE data confines affected deployments to containerized environments - IBM MQ Operator and IBM MQ Advanced Container Images - rather than traditional MQ installations. No public exploit code or confirmed active exploitation was identified at time of analysis, and the mandatory authentication step sharply limits exposure to insiders or attackers who have already obtained MQ credentials.
IBM MQ Operator and MQ Advanced container images can be driven into a denial-of-service condition by an authenticated queue-manager user who submits a specially crafted message that forces excessive memory operations during character-set (CCSID) conversion; the CVSS 3.1 score is 5.3 with an all-availability impact, high attack complexity, and low privileges required. No public exploit code or confirmed active exploitation was identified at time of analysis, and EPSS data was not provided, so this is a moderate-severity, low-priority issue rather than an urgent threat. Impact is confined to service disruption - there is no confidentiality or integrity exposure from the conversion fault itself.
IBM i versions 7.3 through 7.6 contain an improper authorization flaw in the NFS server that allows a local, authenticated low-privilege attacker to bypass configured NFS export version restrictions. The vulnerability requires the NFS server to be configured with version-restricted exports to have any impact, and exploitation is limited to bypassing version controls with low confidentiality and integrity impact. This moderate-severity issue (assessed CVSS 5.4, AV:L) has no public exploit identified at time of analysis, and a vendor patch is available.
IBM i releases 7.3, 7.4, 7.5, and 7.6 can disclose sensitive information to a local attacker who already holds an authenticated low-privileged account, because file handle resolution omits necessary subtree checks and therefore fails to enforce the directory hierarchy boundary. The vendor CVSS vector rates the issue at 5.4 (network-vector, PR:L), but the independent assessment re-scopes it to a local attack (AV:L) with confidentiality-only impact, meaning an attacker needs an existing foothold on the system rather than unauthenticated remote access. There is no public exploit code identified at time of analysis and the issue is not confirmed actively exploited (not in CISA KEV); EPSS data was not provided, so risk is best treated as moderate with a low likelihood of mass exploitation and a higher payoff for an insider or post-compromise attacker seeking data outside their authorized subtree.
Distributed transaction manipulation in IBM i 7.3, 7.4, 7.5, and 7.6 stems from improper validation of attacker-supplied transaction identifiers, allowing a remote, unauthenticated attacker to alter the state of distributed (two-phase commit / XA-style) transactions that the system participates in. The impact is limited to integrity (CVSS 3.1 base score 3.7, AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N) with no confidentiality or availability effect, and high attack complexity means the attacker must know or predict valid transaction identifiers rather than send arbitrary input. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation; a vendor patch is available, so patched systems are not exploitable.
IBM i releases 7.3, 7.4, 7.5, and 7.6 contain an improper authentication weakness that lets a remote attacker who already holds valid IBM i credentials bypass intended security restrictions and read limited information they should not be able to access. The flaw is network-reachable with low attack complexity and no user interaction (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, score 4.3), but it cannot be triggered by an unauthenticated outsider, so realistic risk is confined to malicious insiders or attackers who have already obtained a low-privileged account. No public exploit code and no confirmed active exploitation have been identified at time of analysis, and IBM has published vendor-supplied fixes.
IBM i releases 7.3, 7.4, 7.5 and 7.6 can allow a remote authenticated attacker to slip past the ChrootDirectory confinement that is supposed to isolate SSH/SFTP users, exposing files and data outside the directory they were meant to be restricted to. The weakness is entirely dependent on configuration: it only affects systems that explicitly set ChrootDirectory in sshd_config and rely on it as an isolation boundary, while default deployments without chroot confinement are not impacted. No public exploit code has been identified at time of analysis, and because a valid restricted-account credential is mandatory and the assessed impact is bounded to low confidentiality and integrity loss with no availability effect, this rates as a moderate, operator-dependent issue rather than an emergency.
Denial of service in IBM i's Digital Certificate Manager (DCM) for System TLS allows a local, high-privileged attacker to prevent secure network connections from starting or cause fallback to non-secure connections. Affected versions are IBM i 7.3, 7.4, 7.5, and 7.6. No public exploit code or active exploitation has been identified at time of analysis, and the requirement for authenticated, high-privilege local access makes this a moderate-severity, low-urgency issue.
Improper verification of cryptographic signatures in IBM Db2 Genius Hub 1.0 allows local attackers to bypass JWT signature validation, leading to partial information disclosure and data integrity loss. The flaw requires local access (AV:L) with no authentication or user interaction, but its impact is limited to low confidentiality and integrity (C:L/I:L), making it a moderate-severity, lower-priority issue. No public exploit has been identified, and IBM has released a patch.
Missing initialization vector handling in IBM Db2 Genius Hub 1.0 allows a remote authenticated attacker holding low privileges to weaken the product's cryptographic protection and bypass security restrictions, resulting in a limited integrity impact. Exploitation is constrained by high attack complexity - the attacker must be able to observe or influence the affected ciphertext and benefit from favorable conditions such as repeated or predictable plaintext - and there is no confidentiality or availability impact. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the overall risk is low (CVSS 3.1 base score 3.1).
In the Linux kernel, the following vulnerability has been resolved: powerpc: Do not restore KUAP in arch_exit_to_user_mode_prepare() KUAP means kernel cannot touch user memory unless it explicitly is enabled. In the kernel it should stay AMR_KUAP_BLOCKED. While returning to userspace just before RFI, kernel should restore the user AMR value back. Looks like GENERIC_ENTRY might be treating arch_exit_to_user_mode_prepare() as the last architecture step before returning to userspace. commit bee25f97ad24 ("powerpc: Enable GENERIC_ENTRY feature") therefore called kuap_user_restore() from that hook. But on PowerPC that is too early. After irqentry_exit() / syscall_exit_to_user_mode() we still run platform specific exit routines. e.g. code snippets showing both exception handling and system call handling as the callers of function arch_exit_to_user_mode_prepare() which does kuap_user_restore(). The below path shows that calling kuap_user_restore() is too early when called from arch_exit_to_user_mode_prepare(). Exception handling in exceptions-64s.S ======================================= bl CFUNC(do_page_fault) ..DEFINE_INTERRUPT_HANDLER_ASYNC(do_page_fault) arch_interrupt_async_enter_prepare(regs); state = irqentry_enter(regs); instrumentation_begin(); irq_enter_rcu(); handler(regs); nap_adjust_return(regs); irq_exit_rcu(); instrumentation_end(); arch_interrupt_async_exit_prepare(regs); irqentry_exit(regs, state); <<< too early irqentry_exit_to_user_mode() __exit_to_user_mode_prepare(regs, EXIT_TO_USER_MODE_WORK_IRQ); arch_exit_to_user_mode_prepare(regs, ti_work); <<< too early b interrupt_return_srr .. bl CFUNC(interrupt_exit_user_prepare) <<< already calls kuap_user_restore prep_irq_for_enabled_exit() retry can run kernel code with IRQs on. So only when that routine is fully finished is when the user KUAP should be fully restored which interrupt_exit_user_prepare() already takes care of before returning. Similarly for system call handling in interrupt_64.S ====================================================== bl CFUNC(system_call_exception) .Lsyscall_exit: addi r4,r1,STACK_INT_FRAME_REGS li r5,0 /* !scv */ bl CFUNC(syscall_exit_prepare) .. kuap_assert_locked(); syscall_exit_to_user_mode(regs); <<< too early syscall_exit_to_user_mode_prepare(regs); <<< too early kuap_user_restore(regs); <<< already calls syscall_exit_prepare(), which can enable IRQs, replay a pending interrupt, and only then rfi. Those functions already restore KUAP immediately before rfi. Note that if we restore the user AMR too early like in the current code as shown from the code snippets above, then we get the following warning when CONFIG_PPC_KUAP_DEBUG is enabled: WARNING: arch/powerpc/include/asm/book3s/64/kup.h:293 at interrupt_exit_user_prepare+0x1a0/0x1c0 Hardware name: IBM pSeries (emulated by qemu) POWER10 (architected) TRAP: 0700 LR: c00000000000d8d4 CTR: c0000000021fe500 MSR: <SF,EE,ME,IR,DR,RI,LE> CR: 44000804 XER: 20040000 interrupt_exit_user_prepare+0x1a0/0x1c0 interrupt_return_srr_user+0x8/0x12c
Directory traversal in IBM WebSphere Application Server - Liberty (versions 17.0.0.3 through 26.0.0.9) lets a local, authenticated attacker who can deploy application archives write files outside the intended application directory by embedding crafted path entries in an archive. The attack is constrained rather than remote: the assessed vector is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N (5.5), meaning the attacker must already hold local access and application-deployment privileges, and the only impact is integrity (file write) with no confidentiality or availability loss. This is a moderate-severity, low-urgency issue rather than a top priority; no public exploit identified at time of analysis and no confirmed actively exploited (CISA KEV) status.
Man-in-the-middle interception of traffic from the IBM WebSphere Application Server - Liberty administrative client (versions 17.0.0.3 through 26.0.0.9) can expose sensitive information, because the client does not properly validate TLS certificates (CWE-295). The flaw is rated CVSS 6.5 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N): no authentication or user interaction is required, but exploitation demands that an attacker already occupy a position on the network path - a shared LAN segment, hostile Wi-Fi, compromised gateway or proxy, or an internal lateral foothold - making it a moderate-severity information-disclosure issue rather than a top-tier priority. There is no public exploit identified at time of analysis and the issue is not reported as confirmed actively exploited (CISA KEV); internet-only attackers with no interception capability cannot trigger it.
Information disclosure in IBM WebSphere Application Server - Liberty 17.0.0.3 through 26.0.0.9 lets an authenticated remote user retrieve sensitive server information when the restConnector-2.0 administrative feature is enabled. Rated CVSS 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), the issue requires valid credentials against the management interface and results in confidentiality loss only, with no integrity or availability impact; because restConnector-2.0 is not part of a minimal default Liberty server, deployments that never enabled it are not exposed. No public exploit code and no confirmed active exploitation were identified at time of analysis, making this a moderate-priority issue rather than an emergency.
Information disclosure in IBM WebSphere Application Server - Liberty (versions 17.0.0.3 through 26.0.0.9) lets a principal holding only the read-only Reader role send a crafted request to the version-information retrieval path and cause an uncaught exception, rooted in an integer overflow flaw (CWE-190), that exposes version data. Rated CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N), the impact is limited to low-sensitivity information disclosure with no stated effect on integrity or availability, and exploitation is not remote-unauthenticated - the attacker must already possess or have compromised a low-privilege authenticated account. No public exploit code and no CISA KEV entry were identified at the time of analysis.
Privilege escalation in IBM WebSphere Application Server Liberty (versions 17.0.0.3 through 26.0.0.9) allows an authenticated low-privileged user to bypass authorization checks and carry out management operations beyond their assigned role, but only on servers where the optional restConnector-2.0 feature has been explicitly enabled. It carries a medium CVSS 3.1 score of 5.4 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N) as a CWE-863 improper authorization flaw, meaning credentials are required, no user interaction is needed, and impact is limited to low confidentiality and integrity loss with no availability impact. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and the exposure is meaningfully limited because a bare default server.xml does not enable this connector.
Stored cross-site scripting in IBM's MCP Context Forge (versions 0.2.0 up to but not including 0.3.1) lets an authenticated user who can create or save a Global Prompt store markup with script-capable event handlers, which then executes in the browser of any other user who views that saved prompt in the MCP Admin UI. Successful exploitation can rewrite the interface, display phishing content, capture keystrokes reachable by the page, and perform actions with the victim's browser session, but it requires a valid account, an enabled Admin UI, and a second user to open the prompt. There is no public exploit identified at time of analysis, no KEV listing, and the vendor-released patch in version 0.3.1 (commit acd1619, PR #337) also flips MCPGATEWAY_UI_ENABLED and MCPGATEWAY_ADMIN_API_ENABLED to false by default, removing the surface entirely for patched deployments.
Improper access control in IBM i 7.3, 7.4, 7.5, and 7.6 allows a local attacker who already holds a valid account on the system to trigger a denial-of-service condition, while the supplied impact metrics also point to a low-severity information exposure. The issue carries a moderate CVSS score of 5.3, and there is no CISA KEV listing, no EPSS score provided, and no public exploit code identified at time of analysis, so this should be treated as a low-urgency, locally-privileged defect rather than an active threat. Defenders should note that the published vector (AV:N/PR:N, C:L, A:N) contradicts both IBM's own 'local attacker' description and our assessed vector (AV:L/PR:L), and also fails to express an availability impact despite the denial-of-service wording - this is a data-quality conflict that should be resolved with IBM before assuming network-facing exposure.
User profile enumeration in IBM i 7.3, 7.4, 7.5, and 7.6 allows unauthenticated remote attackers to determine which user profiles exist by observing distinct error codes returned during the sign-on process. The issue requires only network reachability to an exposed IBM i sign-on interface - no credentials and no user interaction (CVSS 3.1 base 5.3, AV:N/AC:L/PR:N/UI:N, C:L only) - and yields nothing beyond confirmation of valid profile names, so it is a reconnaissance weakness rather than a compromise vector. No public exploit code has been identified at time of analysis, the vulnerability is not listed in CISA KEV, and IBM has published a fix.
Brute-force credential guessing against IBM i authentication interfaces can let remote attackers recover valid user credentials, because the platform fails to sufficiently restrict repeated authentication attempts. IBM i releases 7.3, 7.4, 7.5, and 7.6 are affected, and exploitation is unauthenticated (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, base score 5.3), requiring only network reachability to an exposed sign-on endpoint and an account whose password is weak enough to be guessed. This is a moderate-severity weakness rather than a remote code execution or integrity-impacting flaw; no public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV, though any organization exposing IBM i authentication services to untrusted networks should prioritize the vendor fix and tighten lockout and rate-limiting controls.
Local users on IBM i 7.3, 7.4, 7.5, and 7.6 can modify the system BOOTP table because the operating system fails to enforce a proper authority check on that configuration function, a case of improper privilege management (CWE-269). Exploitation requires an interactive or authenticated local presence on the host with at least low-level privileges (CVSS vector AV:L/PR:L), so neither a remote nor a fully unauthenticated attacker can trigger it, and the resulting impact is capped at low confidentiality and low integrity with no availability effect (CVSS 4.4). No public exploit code has been identified at time of analysis and there is no evidence of active exploitation, though IBM has published a vendor fix; this is a low-to-moderate priority issue rather than a top-tier emergency, with exposure scaling with the number of local accounts permitted on the partition.
Cross-site scripting in IBM i 7.3, 7.4, 7.5, and 7.6 allows an authenticated remote user to inject arbitrary script into content that is later rendered by another user's browser, because user-supplied input is not properly validated before being included in a page. Exploitation is not automatic: an attacker must already hold an authenticated session on the system and a separate victim must view or interact with the injected output, so this is not a default-configuration, unauthenticated remote exploit. IBM has published a fix through its support portal, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Exposure of JavaScript source map files in IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 lets remote attackers retrieve the original, unminified client-side source of the web application, exposing internal identifiers, endpoint references, comments and other development-time detail. Per the assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) no authentication or user interaction is required, and the impact is confined to a low-severity confidentiality loss - reconnaissance material rather than direct access, since integrity and availability are unaffected. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and EPSS data was not provided; the vendor itself scored the attack vector as adjacent (AV:A), which would further limit exposure to attackers on the same local or logical network segment. This is a low-priority finding that is nonetheless a confirmed, genuinely disclosed product weakness.
Local information disclosure in IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 allows an attacker who already has access to the host to read sensitive data by abusing a service account that was configured with excessive permissions. The flaw is a privilege-assignment problem (CWE-250) rather than a memory-safety or injection bug: because the service account holds rights beyond what it needs, anything reachable by that account - files, directories, or configuration - becomes reachable to a local user. Impact is confidentiality-only (C:H with I:N/A:N on CVSS 3.1, base 6.2, AV:L/AC:L/PR:N/UI:N), so no tampering or denial of service is involved, there is no network attack path, and there is no public exploit identified at time of analysis; IBM has published a fix referenced in advisory node/7291755.
Cleartext transmission of sensitive information in IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 can allow a local attacker who can observe the relevant channel to obtain limited sensitive information. The assessed vector is CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, meaning exploitation requires local access and no authentication or user interaction but only affects confidentiality; the CVE record lists a base score of 5.1. No public exploit identified at time of analysis, and a vendor patch is available per IBM's advisory.
Stored cross-site scripting in IBM Planning Analytics 2.0 and 2.1 allows an authenticated user holding a valid account on the Web UI to persist arbitrary JavaScript into a stored field, which then executes in the browser of any other user who views that content - potentially disclosing credentials or session data within a trusted session. Per the assessed vector (CVSS 6.4, AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N), exploitation requires both the attacker's existing authenticated access and a second victim user viewing the affected page, and impact is bounded to low confidentiality and integrity within the browser session rather than server-side code execution or availability loss. There is no public exploit code, no CISA KEV listing, and no EPSS score in the available intelligence, so the flaw rates as 'no public exploit identified at time of analysis'.
Cross-site scripting in IBM Planning Analytics 2.0 and 2.1 allows remote attackers to execute arbitrary JavaScript in a victim's browser session by supplying content that is rendered without proper output encoding. Per the supplied CVSS vector (AV:N/AC:L/UI:R/S:U/C:L/I:L/A:N, base 5.4), exploitation requires the victim to interact with or load the attacker-influenced page, and impact is confined to that user's browser context rather than the underlying host or other accounts. No public exploit identified at time of analysis, and no exploitation activity is recorded in CISA KEV; patch available per vendor advisory. Note that the vector's PR:N conflicts with IBM's description of a 'remote authenticated attacker', so authentication requirements are not confirmed from available data and should be verified against IBM support node 7291604.
IBM DataStage on Cloud Pak for Data 5.4.0.0 exposes sensitive information to users who are not authorized to see it, letting an attacker who already holds a valid low-privilege account read data outside their intended scope over the network with no user interaction and low attack complexity. The independent assessment rates the flaw as confidentiality-only (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), so integrity and availability are not affected and the practical limiting factor is the requirement for authenticated access plus network reachability of the Cloud Pak for Data instance - this is not an anonymous, pre-authentication attack. The one caveat worth flagging is that IBM's own vector (9.6, S:C/I:H/I:H) asserts scope change and integrity impact that our assessment does not corroborate from the advisory text; there is no public exploit code and no CISA KEV entry, so there is no public exploit identified at time of analysis, and IBM has published a vendor advisory with patch guidance.
Local information disclosure in Code for IBM i (the codefori/vscode-ibmi Visual Studio Code extension) before 3.0.1 lets other local accounts on the same host read sensitive content written to the shared /tmp directory during Object Browser downloads and the edit-save workflow, because those files are not reliably cleaned up after use. Although the vendor scored it 5.1 on a CVSS:4.0 vector carrying AV:N, exploitation in practice requires an attacker who already holds a separate local account on a shared multi-user machine with a readable /tmp (a common default on many Unix/Linux systems) plus a legitimate developer having performed a download or edit-save in a vulnerable version; single-user workstations and hosts with per-user private temp directories are not affected. Our independent assessment rates it CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N - a low-to-medium risk, confidentiality-only issue - and there is no public exploit identified at time of analysis.
Code injection in IBM Maximo Application Suite's Location Service for Esri component (versions 9.0, 9.1, and 9.2) allows an authenticated attacker with high privileges (CVSS PR:H) and network access to supply an unsanitised container image configuration in the Kubernetes operator template, which the operator may then deploy. The issue is rated CVSS 6.5 Medium (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N) and can lead to high confidentiality and integrity impact, but requires privileged access to the MAS environment and affects an optional component. No public exploit identified at time of analysis, and no KEV or EPSS data indicates active exploitation.
Connection-resource exhaustion in IBM Power Systems firmware levels FW1110.00 through FW1110.31, FW1120.00 through FW1120.01, and FW1060.00 through FW1060.81 lets a highly privileged attacker on an adjacent network segment drive a denial of service by consuming connections the service processor never releases, until legitimate management traffic can no longer be serviced. The assessed vector (CVSS 4.5, AV:A/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H) means exploitation requires pre-existing administrative access to the affected interface plus network adjacency to the management segment, which confines realistic risk to insiders or attackers who have already established a foothold on the management network; confidentiality and integrity are unaffected. No public exploit has been identified at time of analysis and there is no indication of active exploitation, making this a low-to-moderate priority availability issue rather than an urgent one.
Improper input validation in IBM Db2 11.5.0 through 11.5.9 and 12.1.0 through 12.1.5 lets a local attacker who already holds authenticated low-privilege access to the database host or instance disrupt the affected component, resulting in a limited availability impact. The issue is not remotely reachable and cannot be triggered by an unauthenticated user; our assessment rates it CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L, a low-severity availability-only condition, and there is no public exploit identified at time of analysis. Overall this is a low-priority, low-real-risk issue despite being a named CVE, and vendor patching is available.
Denial of service in IBM Db2 11.5.0 through 11.5.9 and 12.1.0 through 12.1.5 can be triggered by an authenticated, low-privileged user (PR:L) submitting a specially crafted query that references a Materialized Query Table, causing a stack-based buffer overflow (CWE-121) that crashes the database engine. IBM has released a patch; no public exploit identified at time of analysis, and impact is limited to availability with no data disclosure or modification. Note that IBM's CVSS vector indicates local access (AV:L), while the query-execution nature suggests a remote authenticated client may be able to trigger the flaw, pending confirmation with the vendor.
Reflected cross-site scripting in IBM DB2 Recovery Expert for Linux, UNIX and Windows 5.5 IF 2 lets an unauthenticated attacker inject arbitrary JavaScript into the product's Web UI, which then executes in the browser of a logged-in user within a trusted session and can lead to credential or session disclosure. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N, score 6.1) shows the attacker does not need to authenticate, but a victim with an active session must be induced to trigger the reflected payload, making user interaction the primary limiting factor and the practical risk moderate-to-low. No public exploit code or confirmed active exploitation has been identified at time of analysis, and a vendor patch is available (CWE-79).
Reflected cross-site scripting in IBM Db2 Recovery Expert for Linux, UNIX and Windows 5.5 IF 2 allows an unauthenticated attacker to embed arbitrary JavaScript in the Web UI, which executes in the browser of a victim operator who interacts with the crafted content and can lead to disclosure of credentials from a trusted session. The flaw is rated CVSS 6.1 (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N), meaning no attacker authentication is needed but the payload only fires after a legitimate user opens or interacts with the injected content, so this is not a drive-by, self-propagating compromise. Exploitation status is assessed as no public exploit identified at time of analysis, with no CISA KEV listing; the practical exposure is limited by the mandatory user interaction, the narrow deployment base of this recovery tooling, and the fact that only the specific 5.5 IF 2 build is in scope.
Reflected cross-site scripting in IBM Db2 Recovery Expert for Linux, UNIX and Windows 5.5 IF 2 Web UI allows unauthenticated remote attackers to inject arbitrary JavaScript into a victim's trusted session, potentially leading to credential disclosure. The CVSS 3.1 base score is 6.1 (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N); no public exploit was identified at time of analysis. A vendor patch is available, and successful exploitation requires a logged-in operator to interact with attacker-supplied input.
Untrusted external web-link handling in IBM Db2 Recovery Expert for Linux, UNIX and Windows 5.5 Interim Fix 2 allows a remote, unauthenticated attacker to craft a link that can expose sensitive information or trigger unauthorized actions inside a victim's browser (CWE-1022). The flaw cannot be triggered server-side or automatically: it requires the victim to click an attacker-supplied link that resolves through the application's untrusted external reference, so the practical barrier is social engineering rather than authentication (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N, score 6.1). Impact is confined to the victim's browser context rather than the Db2 Recovery Expert host, and no public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis.
Denial of service in IBM Db2 11.5.0 through 11.5.9 and 12.1.0 through 12.1.5 can be triggered by an authenticated user who holds INSERT privileges on a table containing one or more XML columns, potentially crashing or hanging the database instance under conditions IBM has not fully quantified. The flaw is classified as uncontrolled resource consumption (CWE-770) and carries a CVSS 3.1 score of 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), meaning the impact is confined to availability with no confidentiality or integrity loss. Exploitation requires a valid Db2 session (PR:L) and typical SQL INSERT access, but no public exploit code has been identified at time of analysis and there is no indication of active exploitation; this is a moderate-priority availability issue rather than a critical emergency. Vendor patches are available per IBM's advisory.
Local privilege escalation in IBM Db2 11.5.0-11.5.9 and 12.1.0-12.1.5 allows an authenticated low-privileged user on the database host to abuse the db2pd monitoring and diagnostic utility to gain privileges beyond those they legitimately hold. Exploitation requires pre-existing local shell access and the ability to run db2pd, so the flaw is not reachable remotely or by unauthenticated actors; it matters most on shared, multi-tenant, or otherwise privileged-access Db2 servers. Our independent assessment rates the true impact higher than IBM's published CVSS 6.5, scoring it CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H; no public exploit code has been identified and the issue is not confirmed as actively exploited (not in CISA KEV), though a vendor patch is available and should be applied to remove the condition.
Denial of service in IBM Guardium Data Protection 12.2.2 allows remote unauthenticated attackers to degrade availability by racing concurrent unsynchronized writes to a shared map. The supplied CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 7.5) describes availability-only impact with no confidentiality or integrity loss; our assessment refines attack complexity to AC:H because the non-deterministic race window reduces reliability below AC:L. No public exploit identified at time of analysis, and a vendor patch is available via IBM Support node 7288627, so patched or non-12.2.2 deployments are not exposed.
Denial of service in IBM Guardium Data Protection 12.2 is achievable by an authenticated remote attacker using path traversal sequences against a network-reachable component, with high integrity and availability impact (CVSS 3.1 base 8.1). The CVSS vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H confirms the attacker needs only low-privilege credentials, no user interaction, and low attack complexity, so the main barrier is obtaining a valid Guardium account. No public exploit identified at time of analysis, and the supplied data does not confirm active exploitation or CISA KEV listing.
Cleartext storage of sensitive information in IBM Guardium Data Protection 12.0, 12.1, and 12.2 application logs allows a local, authenticated low-privileged user with read access to those log files to obtain limited sensitive data (CWE-532). IBM rates this at a CVSS 3.1 base score of 3.1, but the network attack vector in the vendor vector overstates real-world reachability: exploitation depends on an existing local foothold on the appliance and on sensitive values being written to logs only intermittently or conditionally, so impact is confined to limited confidentiality disclosure with no integrity or availability effect. There is no public exploit identified at time of analysis, and a vendor patch is available.
High-privileged, already-authenticated administrators on the management interface of IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 can forge or tamper with audit log records by injecting argument delimiters into the logging functionality (CWE-88). Because the CVSS vector is PR:H, only an account that already holds elevated privileges on the management console can reach the affected feature, so realistic exposure is confined to insider misuse or an attacker who has already stolen a privileged credential; no user interaction is required and the interface is network-reachable, but impact is limited to audit log integrity with no confidentiality or availability effect. There is no vendor indication of exploitation, and no public exploit identified at time of analysis; severity is low (CVSS 2.7), and a patch is available per the vendor advisory.
SQL injection (CWE-89) in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 allows a remote attacker holding a valid low-privileged session to inject SQL through standard authenticated functionality, enabling unauthorized modification of backend data and partial denial of service. The vendor-assigned CVSS 3.1 score is 5.4 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L), so confidentiality is not assessed as impacted; the practical barrier is the requirement for credentials, not a special configuration. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and IBM has published a fix via its support portal.
Cross-site scripting (CWE-79) in the Web UI of IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 - including their container editions - lets an attacker inject arbitrary JavaScript into pages rendered by the interface, which can execute in the browser of an authenticated administrator or operator with an active trusted session and potentially disclose credentials or session data. The injection itself requires no authentication (the supplied vector is PR:N), but the payload is only harmful when a victim loads the crafted content (UI:R), so exploitation depends on a successful lure, a poisoned page, or injection into a view the victim already opens. IBM rates this 8.2 (scope changed, high confidentiality and integrity impact); no public exploit code or active exploitation has been identified at time of analysis, though the faulted UI is a high-value administrative target. Note a vector discrepancy: the published CVSS marks AV:L whereas the independent assessment scores AV:N, so defenders should confirm with IBM whether the affected UI is reachable remotely or only from a local/management network, since that materially changes exposure.
Security restriction bypass in IBM Security Verify Access (10.0 through 10.0.9.2) and IBM Verify Identity Access (11.0 through 11.0.3), including their container images, lets a remote attacker who already holds a valid low-privilege session circumvent authentication controls and gain high confidentiality and integrity impact (CVSS 3.1 base 8.1, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N). Because the vector is PR:L, anonymous or unauthenticated attackers cannot trigger this on their own; the attacker must first possess valid credentials or a session, after which the bypass is low-complexity, requires no user interaction, and is reliably reproducible. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (no CISA KEV listing), but a vendor patch is available, so the issue should be treated as a credible, above-average-priority fix rather than an emergency.
An authenticated user can exhaust server resources in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3, including the containerized editions, by submitting a specially crafted HTTP query that triggers uncontrolled resource allocation, resulting in a denial of service (CVSS 3.1 base 6.5, AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H). Exploitation requires a valid authenticated session on the affected HTTP interface (PR:L); there is no confidentiality or integrity impact, only availability. No public exploit code was identified at time of analysis and the issue is not listed in CISA KEV, so this is a moderate-priority availability defect rather than a top-tier emergency; vendor patching is available per IBM's advisory.
Authentication workflow bypass in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 allows a remote authenticated attacker who already holds valid first-factor credentials or an active session to skip the configured additional authentication workflow steps - such as step-up authentication, multi-factor prompts, or multi-step policy flows. Rated CVSS 6.5 (moderate), the flaw only affects deployments that actually enforce an additional authentication workflow; environments without one have nothing for the bypass to defeat. Exploitation requires the extra-workflow feature to be configured and the attacker to be a remote authenticated actor, and no public exploit code or confirmed in-the-wild exploitation has been identified at time of analysis; note that IBM's supplied CVSS vector (PR:N) contradicts its own 'remote authenticated attacker' description and our independent assessment, which uses PR:L and should be reconciled with the vendor.
A remote, unauthenticated attacker can trigger a limited heap-based out-of-bounds read in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3, including their container editions, by sending a specially crafted request to an exposed instance. Successful exploitation is confined to a partial memory read that can cause a denial-of-service condition; there is no confidentiality or integrity impact and no code execution path described. This is a low-severity issue (CVSS 3.1 base 3.7, AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L) that should be treated as low priority despite its network-facing nature, and at time of analysis no public exploit code and no confirmed active exploitation were identified; a vendor patch is available via IBM support node 7291628.
Authenticated cross-site scripting (XSS) in the local management interface of IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 allows a low-privileged authenticated user to embed arbitrary JavaScript into the Web UI when the deployment is in certain non-default configurations, potentially altering the interface's intended behaviour and disclosing credentials within a trusted session. Exploitation requires an existing account on the management interface (CVSS PR:L) and, in practice, a second trusted user such as an administrator who renders the injected content in their own session; no public exploit code and no confirmed active exploitation were identified at time of analysis. The issue is rated low-to-moderate priority - network-reachable but gated by high attack complexity (AC:H) attributable to the configuration prerequisite and by user interaction in the assessed vector.
Cross-site scripting in the IBM Security Verify Access (10.0 through 10.0.9.2) and IBM Verify Identity Access (11.0 through 11.0.3) Web UI allows an authenticated user to embed arbitrary JavaScript into a field that is later rendered to another user, so the payload executes within that victim's trusted session (scope change, S:C) and can lead to credential or session disclosure. The CVSS vector (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N, score 5.4) confirms remote reachability but requires a valid low-privileged account plus victim interaction; there is no availability impact and the exposure is limited to data reachable inside the victim's session. No public exploit code exists and there is no confirmed active exploitation (CISA KEV) at the time of analysis; a vendor patch is available per the IBM advisory.
Stored cross-site scripting in IBM Guardium Data Protection 12.2 lets an unauthenticated attacker who can influence traffic on a database that Guardium monitors plant a malicious script that later executes in the browser of a logged-in Guardium operator when the Quick Search results grid renders the stored payload (CWE-79). IBM rates this CVSS 9.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N), but an independent reassessment places it at CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N because the victim must actively open the Quick Search grid and hold an authenticated, privileged console session - a real limiting factor the vendor's UI:N rating does not capture. Exploitation therefore requires two conditions together: attacker-controlled data must reach the monitored database traffic Guardium ingests, and a Guardium user must subsequently view those results; no public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV).
IBM Guardium Data Protection 12.2.2 writes SECRET and API_KEY credential material into INFO-level logs produced by the edge-controller and edge-manager components during credential rotation, so an authenticated attacker who can read those application or container logs can harvest live service credentials and later use them to impersonate services or reach the Guardium control plane. Exploitation requires prior Guardium authentication (the vector carries PR:L), read access to the affected logs, and that a rotation event occur or be induced so the secret is actually written; no user interaction is involved. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the vendor advisory (IBM support node 7288627) is the primary reference. Because the prerequisite is log readability on the host or container rather than open network reachability, our assessment treats the vector as local (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) even though the vendor scores it AV:N.
IBM Guardium Data Protection 12.0, 12.1 and 12.2 ship the WfpMonitor kernel driver, whose METHOD_NEITHER IOCTL handlers dereference caller-supplied pointers without consistent probing or exception handling, so a local attacker who already holds high privileges on the host can trigger a system crash or obtain limited reads of kernel memory. The CVSS 3.1 vector (AV:L/PR:H/UI:N, C:L/I:N/A:H, score 5.1) confirms the flaw is local-only and requires pre-existing elevated privileges, meaning it grants no privilege escalation and has no integrity or code-execution impact. There is no CISA KEV entry and no public exploit code identified at time of analysis, and a vendor patch is available, making this a moderate-to-low real-world priority that is best handled through routine driver patching.
Signature forgery in IBM DataPower Gateway lets an authenticated user with valid low-privilege credentials submit signature requests that the appliance processes without properly verifying data authenticity, producing forged signatures that relying parties may accept as genuine. Affected firmware spans 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2; the impact is integrity-only (CVSS 3.1 base 6.5, AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N) with no confidentiality or availability loss. There is no public exploit identified at time of analysis, and IBM has published a vendor fix via its support portal, so this is a moderate-risk authenticated integrity issue rather than a remotely exploitable, unauthenticated critical defect.
Stored/reflected cross-site scripting in the administrative Web UI of IBM DataPower Gateway (10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2) lets an authenticated user whose input is rendered back into UI pages embed arbitrary JavaScript that executes in the browser of another, potentially more-privileged user, enabling credential or session disclosure inside the trusted management session. The flaw is not self-executing: it requires a low-privileged authenticated position (PR:L) plus a second victim who views the injected content (UI:R), and there is no public exploit identified at time of analysis, nor is it listed in CISA KEV. At CVSS 5.4 (CWE-79) this is a genuine but non-urgent issue, with realistic risk confined to deployments whose management Web UI is reachable by multiple users of differing privilege levels.
Improper authorization in IBM DataPower Gateway lets a local attacker who already holds a valid low-privileged account read sensitive information that should be restricted from that privilege level. Exposure is limited to specific builds: 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6 (10.6CD), and 11.0.0.0 through 11.0.0.2. Exploitation requires local access to the appliance plus authenticated credentials (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N), so realistic risk is confined to insiders or post-compromise scenarios; CISA SSVC records no known exploitation, no public exploit code is identified at time of analysis, and IBM has published a vendor patch (support node 7289775).
Denial of service in IBM DataPower Gateway (10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2) allows a remote unauthenticated attacker to degrade or stall request processing by submitting input that forces worst-case algorithmic complexity during linked-list traversal. Rated CVSS 5.9 (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H), the flaw is an availability-only issue: the CVSS AC:H rating reflects that the attacker must craft input to hit the pathological code path rather than simply flooding the gateway with arbitrary traffic, and impact is confined to service degradation or denial with no confidentiality or integrity effect. No public exploit identified at time of analysis, and a vendor patch is available.
Denial of service affecting IBM DataPower Gateway builds 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2, where a crafted GraphQL request containing a malformed variable causes a NULL pointer dereference that crashes or hangs the affected service. The flaw is network-reachable and requires no authentication (PR:N) and no user interaction (UI:N), but the HIGH attack complexity (AC:H) means the attacker must craft input that reliably reaches the dereference, so opportunistic mass exploitation is unlikely. Impact is availability-only with no data disclosure or modification, and no public exploit identified at time of analysis; this is a moderate, availability-only issue rather than a top-tier priority.
An out-of-bounds read in IBM DataPower Gateway (CWE-125) lets an attacker who already holds valid credentials on the gateway reach past intended buffer boundaries and have fragments of process memory returned to them, disclosing limited sensitive information. Affected release trains are 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2, as listed in ENISA EUVD-2026-94890 and IBM's advisory node/7289775. The base score is 5.3 with confidentiality-only, low-severity impact and no effect on integrity or availability; IBM's description requires a remote authenticated user, which the independent assessment reflects by treating the vector as PR:L instead of NVD's PR:N. No public exploit code has been identified at time of analysis and there is no CISA KEV entry, so realistic risk is confined to credentialed actors and compromised accounts rather than unauthenticated mass exploitation.
Server-side request forgery in IBM DataPower Gateway (10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2) lets an authenticated user who satisfies high-complexity preconditions make the appliance send requests to destinations of the attacker's choosing, enabling internal network enumeration and reconnaissance that can support follow-on attacks. Rated CVSS 4.9 (AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N), this is a moderate-severity, low-priority issue rather than an emergency: exploitation requires a valid authenticated session plus the ability to reach a request-handling function that accepts an attacker-influenced destination, and there is no public exploit identified at time of analysis, with real-world impact bounded by whatever sensitive internal hosts the gateway itself can reach. IBM has published an advisory covering these builds, and other versions are not in scope.
Path traversal in IBM Langflow OSS 1.0.0 through 1.12.2 lets a remote attacker who holds a valid Langflow account read files outside the intended restricted directory, exposing sensitive data at high confidentiality impact (CVSS 6.5, CWE-22). The flaw is network-reachable, low-complexity and requires no victim interaction, but it cannot be triggered anonymously: the CVSS vector (PR:L) means the attacker must already be able to authenticate to the instance, so risk concentrates on internet-exposed or multi-tenant deployments with loose account provisioning. IBM has published a vendor patch (referenced in its support advisory), and no public exploit code was identified at time of analysis; no KEV listing was provided in the intelligence for this CVE.
Information disclosure in IBM Langflow OSS 1.0.0 through 1.12.2 allows a remote, authenticated attacker holding only low-privilege credentials to obtain sensitive information that should not be reachable from their account, resulting in a high confidentiality impact with no effect on integrity or availability. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N) confirms credentials are required and that no user interaction is needed, while the scope-change metric indicates the exposed data can affect resources beyond the vulnerable component itself. Patch available per vendor advisory; no public exploit identified at time of analysis, and no CISA KEV or EPSS signal was provided. This is a credible mid-tier priority rather than an emergency, and the practical risk hinges on how many low-privilege accounts exist and whether the instance is reachable from untrusted networks.
Authenticated users of IBM Langflow OSS 1.0.0 through 1.12.2 can exhaust server resources by supplying a crafted ZIP archive to a code path that performs extraction, degrading or halting availability of the affected instance (CVSS 3.1 base 4.3, CWE-400). The flaw is reachable over the network by a low-privilege authenticated attacker (AV:N/PR:L/UI:N) and is limited to availability impact (C:N/I:N/A:L), with no data exposure, integrity loss, or code execution demonstrated. This is a low-to-moderate priority issue, not an urgent one: it is not confirmed as actively exploited (no CISA KEV listing) and no public exploit code has been identified at time of analysis, though the mandatory credential requirement means exposure is confined to deployments with reachable ZIP-extraction functionality.
Path traversal in IBM Langflow OSS 1.0.0 through 1.12.2 allows an authenticated remote attacker to read files outside the intended directory, causing high-impact confidentiality loss (CVSS 6.5, C:H/I:N/A:N) without modifying data or disrupting service. Exploitation requires low-privileged credentials (PR:L) but is network-reachable, low-complexity, and needs no user interaction, so multi-tenant or self-registration deployments face elevated risk because obtaining an account is trivial; the flaw is a moderate-severity information-disclosure issue with middle-tier real-world priority. No public exploit code or confirmed active exploitation is identified at time of analysis, and IBM has published a vendor patch advisory.
Arbitrary code execution in IBM Cyber Fraud 1.0.0 through 1.0.2 requires an authenticated low-privilege user to upload a file with a dangerous type and then depends on a victim interacting with that file; the upload handler does not restrict dangerous file types (CWE-434). The vendor CVSS score is 6.8, while the independent assessment rates confidentiality, integrity, and availability impact as high with scope unchanged; the mandatory authentication (PR:L) and user interaction (UI:R) limit anonymous, fully automated exploitation. No public exploit code or CISA KEV entry was identified at time of analysis, and the realistic risk is moderate and context-dependent rather than an emergency.
Server-side request forgery in IBM ContextForge MCP Gateway 0.1.0 through 1.0.5 lets users who hold an authenticated account with gateway-creation privileges direct arbitrary HTTP POST requests at internal network services, localhost-bound daemons, and cloud metadata endpoints (AWS IMDSv1, GCP, Azure). The flaw is reachable only through the OAuth client-credentials gateway registration flow, where the oauth_config.token_url parameter is used without the SSRF validation that already guards the gateway.url field; the gateway then immediately POSTs form-encoded client credentials to the attacker-named URL and, when the reply fails OAuth token parsing, reflects up to 256 characters of the response body in an HTTP 502 error. Exploitation requires valid low-privileged credentials (PR:L) and returns only limited/blind data, no public exploit code was identified at time of analysis, there is no CISA KEV listing, and EPSS is 0.18% (7th percentile) - a moderate, low-priority issue rather than an emergency.
Denial of service in IBM Storage TS4500 Library and IBM Diamondback Tape Library firmware versions 1.1.1.6 through 1.12.0.3 allows an authenticated low-privilege user to exhaust system resources by sending specially crafted SMTP requests to the library's email/notification management interface. The issue is a moderate, not top-tier, priority because authentication is mandatory, impact is limited to availability, and the appliance is typically internal rather than internet-exposed; no public exploit was identified at time of analysis. A vendor patch is available per IBM advisory node/7292612.
IBM Storage TS4500 Library versions 1.1.1.6 through 1.12.0.3 fail to invalidate a session after logout, allowing an authenticated user who obtains or retains a still-valid session identifier to impersonate another user. Exploitation requires a second user to have logged out and the attacker to possess that session token, so impact is limited to multi-user or insider scenarios and the issue is moderate severity/low urgency. Patch is available per IBM advisory node/7292613; no public exploit identified at time of analysis.
IBM TS4500 Library firmware 1.1.1.6 through 1.12.0.3 fails to invalidate sessions, allowing an authenticated attacker who retains a usable session identifier to impersonate another user on the library management interface. CVSS 3.1 scores this 6.3 with vector AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L, meaning exploitation requires an authenticated session and is bounded to limited confidentiality, integrity, and availability impact. No public exploit identified at time of analysis, and IBM has published a vendor patch advisory.
A race condition in IBM Storage TS4500 Library firmware versions 1.1.1.6 through 1.12.0.3 lets a remote, low-privileged authenticated user escalate to administrative privileges by timing an operation against a concurrent privileged action. The flaw is a privilege-escalation issue rather than a pre-authentication bypass, since valid credentials for the library management interface are mandatory, and successful exploitation depends on winning a non-deterministic race that may require repeated attempts. IBM has released a fix; no public exploit code or confirmed active exploitation was identified at time of analysis, and the EPSS-style risk profile places this as a patch-on-a-normal-cycle item.
IBM Cloud Pak System 2.3.6.0 and 2.3.6.1 employ weaker-than-expected cryptographic algorithms, allowing an attacker who obtains the protected ciphertext to decrypt highly sensitive information. The CVSS 5.9 score (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N) reflects that exploitation requires capturing the encrypted data and performing cryptanalysis, which substantially constrains real-world risk despite the unauthenticated network vector. No public exploit code or active exploitation has been identified at time of analysis, and IBM has released a vendor patch.
HTML injection (CWE-80) in IBM Cloud Pak System 2.3.6.0 and 2.3.6.1 lets a remote attacker who already holds valid credentials on the web interface inject malicious HTML/script that executes in another user's browser within the hosting site's security context. Impact is limited to low confidentiality and integrity effects (CVSS 5.4) and requires both a legitimate authenticated account and a victim subsequently viewing the injected content, so it is a routine patch-management item rather than an urgent one. No public exploit code or confirmed active exploitation was identified in the available data; the vendor has published a fix advisory.
Improper certificate validation in IBM Concert 1.0 through 3.0.0 allows an attacker who already holds a man-in-the-middle position to present forged or invalid TLS certificates that the product may accept, yielding low confidentiality and integrity impact with no availability effect. The provided CVSS 3.7 vector requires high attack complexity and user interaction, and the supplied vectors conflict on whether low-level privileges (PR:L) are required, so authentication requirements are not consistently confirmed from the available data; no public exploit code or CISA KEV entry was identified at time of analysis. This is a low-severity issue and the signals are consistent in pointing to limited real-world risk.
Information disclosure in IBM Concert 1.0 through 3.0.0 can expose sensitive heap-resident data to an authenticated local attacker with low privileges who is able to inspect the application's process memory, with high attack complexity and no public exploit identified at time of analysis. The flaw is CWE-244 (failure to clear heap memory before release), rated CVSS 4.7, and a vendor patch is available. Realistic risk is limited to post-compromise or insider scenarios on hosts where an attacker already has local access.
Cross-origin resource sharing (CORS) misconfiguration in IBM Concert 1.0 through 3.0.0 can allow attacker-controlled web content to carry out privileged actions in the context of a victim's authenticated session when the allowed domain is not limited to trusted domains. The vendor rates attack complexity High and impact limited, and the CVSS vector indicates no prior privileges are required (PR:N) even though practical exploitation depends on a victim with an active Concert session loading malicious web content. IBM has released a fix; no public exploit was identified at time of analysis.
Information disclosure in IBM Concert 1.0 through 3.0.0 exposes schema suggestion data to network-reachable attackers; the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) indicates no authentication or user interaction is required, although the impact is limited to low confidentiality loss with no integrity or availability effect. The flaw is rated 5.3 (moderate) and is chiefly useful for reconnaissance rather than direct compromise. No public exploit code or CISA KEV entry was identified at time of analysis, and patch availability is documented in the vendor advisory.
IBM Concert versions 1.0 through 3.0.0 persist web page content to a local on-disk cache that is not adequately protected, so a second user with an account on the same host can read cached page data belonging to another Concert user. The issue is strictly local (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, base score 4.0) and impacts confidentiality only - there is no network attack path, no integrity or availability effect, and single-user or isolated deployments where no other principal can reach the cache are not meaningfully exposed. Exploitation requires an attacker to already hold local/interactive access to the host; no public exploit code has been identified at time of analysis and the issue is not in CISA KEV. A vendor patch is available.
IBM Concert 1.0 through 3.0.0 can expose highly sensitive information because it relies on weaker-than-expected cryptographic algorithms, allowing an attacker who obtains the protected data to attempt to recover plaintext. The CVSS vector (AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N) describes a network-reachable, unauthenticated and no-interaction path, but exploitation is high-complexity and limited to confidentiality impact. No CISA KEV entry and no public exploit were identified at time of analysis, so this is a low-priority cryptography hardening issue rather than an actively exploited intrusion vector.
Log injection in IBM Concert 1.0 through 3.0.0 lets remote unauthenticated attackers corrupt or forge log records by supplying input containing special or control characters that the product writes to its log files without neutralization. The CVSS 3.1 score is 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N), so the only assessed impact is limited integrity damage to log data - there is no code execution, data disclosure, or availability loss. No public exploit code or confirmed active exploitation was identified at time of analysis, and real-world severity depends on how downstream log consumers (viewers, SIEM parsers, audit reviews) handle unescaped content.
Cross-site scripting in the IBM Concert Web UI (versions 1.0 through 3.0.0) lets remote attackers inject arbitrary JavaScript into pages viewed by other users, potentially disclosing credentials from within a trusted session. Exploitation requires the victim to interact with attacker-supplied content - such as clicking a crafted link or loading a page reflecting the payload - while authenticated to Concert, so practical risk is targeted rather than mass exploitation. No public exploit code or confirmed active exploitation is known, and IBM has released a vendor fix; EPSS context is not provided in the available data.
Crafted messages published into IBM MQ 9.4.5.0 or 9.4.5.1 can crash the applications that consume them, giving an authenticated message producer a denial-of-service primitive against queue-processing services. Successful exploitation requires a valid MQ identity with put authority on a queue that a vulnerable consumer reads; the CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, score 6.5) confirms the attacker must be authenticated and that only availability is impacted, with no confidentiality or integrity effect. There is no CISA KEV listing and no public exploit identified at time of analysis, so this should be handled as routine, medium-severity patch management rather than emergency response, especially since deployments outside the 9.4.5.0-9.4.5.1 range are not affected.
Denial of service in IBM MQ client applications that consume messages asynchronously can be triggered when a queue name carrying an improperly validated length value reaches the client, producing a buffer overflow (CWE-120) that crashes or hangs the consuming application. The flaw affects IBM MQ Operator and IBM MQ Advanced Container Images deployments and is reachable either by an attacker who already controls the queue manager or by a man-in-the-middle able to tamper with message metadata on unencrypted, non-TLS channels. IBM has released a vendor patch per its support advisory, no public exploit code or active exploitation has been identified at time of analysis, and the CVSS 5.9 score reflects availability-only impact with high attack complexity.
Denial of service in IBM MQ Operator and IBM MQ Advanced container images lets an authenticated MQ client crash the queue manager by sending an MQOPEN request whose offset values are not properly validated, producing a buffer-handling fault in the queue manager process. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) shows the limiting factor is credentials: the attacker must already hold a valid MQ identity and an established connection able to issue MQ API calls, so exposure is limited to insiders or attackers who have compromised an MQ application identity. Confidentiality and integrity are unaffected, the vendor has published a fix, and no public exploit code or active exploitation has been identified at time of analysis (CISA SSVC exploitation: none, automatable: no).
Authenticated IBM MQ clients can cause a bounded denial of service and obtain limited information about process memory layout in IBM MQ Operator and IBM MQ Advanced Container Images deployments by sending a specially crafted request that triggers an out-of-bounds read. The issue requires a valid MQ client session and network access to the queue manager listener, and impact is limited to availability and low-confidentiality disclosure rather than code execution or data modification. No public exploit was identified at time of analysis, and IBM has published a vendor patch.
Authenticated denial of service in IBM MQ container deployments - specifically the MQ Operator and MQ Advanced container images - lets a remote user who already holds valid MQ credentials crash the queue manager by sending specially crafted multicast status messages that drive the process into a NULL pointer dereference. Impact is availability-only (CVSS 6.5, A:H with C:N/I:N); confidentiality and integrity are unaffected. Exploitation is further constrained because the target deployment must have multicast messaging configured and enabled, a non-default capability absent from most standard queue-manager installations, and no public exploit has been identified at time of analysis.
Authenticated users of IBM MQ Operator and IBM MQ Advanced container image deployments can cause a denial of service against the queue manager by submitting malformed RFH2 message header fields through queued publish/subscribe operations. The flaw is rated CVSS 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), reflecting high availability impact only - there is no disclosure or modification of message data - and requires valid MQ credentials with authorization to publish or subscribe, so anonymous remote parties are not positioned to exploit it. No public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor has published remediation guidance; the practical exposure is limited to environments that both grant the attacker a usable principal and expose queued pub/sub messaging.
Denial of service in IBM MQ Operator and MQ Advanced Container Images allows an authenticated MQ client to crash the queue manager agent by sending a crafted asynchronous consume request that triggers untrusted deserialization (CWE-502). The CVSS 6.5 vector confirms network reachability, low privileges (PR:L), no user interaction, and availability-only impact; confidentiality and integrity are unaffected, and this is a moderate-priority availability issue rather than a top-tier emergency. No public exploit was identified at time of analysis, CISA SSVC rates exploitation as none and automatable as no, and IBM has published a vendor patch.
Path traversal in IBM MQ Web Console allows an authenticated administrator to write files outside the intended directory in deployments using IBM MQ Operator or IBM MQ Advanced Container Images. The issue is low severity (CVSS 2.7) with integrity-only impact and a high privilege prerequisite, and no public exploit identified at time of analysis; a vendor patch is available per IBM advisory.
Malformed compressed message data delivered to containerized IBM MQ deployments (MQ Operator and MQ Advanced Container Images) can drive a minor out-of-bounds read (CWE-125) in the decompression code path, but the broker rejects the malformed request and does not return the over-read bytes, so no message or memory contents are exposed. The attacker must already hold valid MQ connection credentials (CVSS PR:L) and clear high attack complexity (AC:H) by crafting a specific malformed compressed structure, keeping the issue at CVSS 3.1 (Low). No public exploit code or active exploitation has been identified at time of analysis, and IBM has published a vendor fix via its support portal.
Authenticated IBM MQ users holding valid queue-manager credentials can trigger an off-by-one buffer overflow by submitting a specially crafted object name, causing process instability or a crash of MQ components. The impact is availability-only (CVSS 4.3, PR:L, A:L) with no path to data disclosure or code execution, and the CPE data confines affected deployments to containerized environments - IBM MQ Operator and IBM MQ Advanced Container Images - rather than traditional MQ installations. No public exploit code or confirmed active exploitation was identified at time of analysis, and the mandatory authentication step sharply limits exposure to insiders or attackers who have already obtained MQ credentials.
IBM MQ Operator and MQ Advanced container images can be driven into a denial-of-service condition by an authenticated queue-manager user who submits a specially crafted message that forces excessive memory operations during character-set (CCSID) conversion; the CVSS 3.1 score is 5.3 with an all-availability impact, high attack complexity, and low privileges required. No public exploit code or confirmed active exploitation was identified at time of analysis, and EPSS data was not provided, so this is a moderate-severity, low-priority issue rather than an urgent threat. Impact is confined to service disruption - there is no confidentiality or integrity exposure from the conversion fault itself.
IBM i versions 7.3 through 7.6 contain an improper authorization flaw in the NFS server that allows a local, authenticated low-privilege attacker to bypass configured NFS export version restrictions. The vulnerability requires the NFS server to be configured with version-restricted exports to have any impact, and exploitation is limited to bypassing version controls with low confidentiality and integrity impact. This moderate-severity issue (assessed CVSS 5.4, AV:L) has no public exploit identified at time of analysis, and a vendor patch is available.
IBM i releases 7.3, 7.4, 7.5, and 7.6 can disclose sensitive information to a local attacker who already holds an authenticated low-privileged account, because file handle resolution omits necessary subtree checks and therefore fails to enforce the directory hierarchy boundary. The vendor CVSS vector rates the issue at 5.4 (network-vector, PR:L), but the independent assessment re-scopes it to a local attack (AV:L) with confidentiality-only impact, meaning an attacker needs an existing foothold on the system rather than unauthenticated remote access. There is no public exploit code identified at time of analysis and the issue is not confirmed actively exploited (not in CISA KEV); EPSS data was not provided, so risk is best treated as moderate with a low likelihood of mass exploitation and a higher payoff for an insider or post-compromise attacker seeking data outside their authorized subtree.
Distributed transaction manipulation in IBM i 7.3, 7.4, 7.5, and 7.6 stems from improper validation of attacker-supplied transaction identifiers, allowing a remote, unauthenticated attacker to alter the state of distributed (two-phase commit / XA-style) transactions that the system participates in. The impact is limited to integrity (CVSS 3.1 base score 3.7, AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N) with no confidentiality or availability effect, and high attack complexity means the attacker must know or predict valid transaction identifiers rather than send arbitrary input. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation; a vendor patch is available, so patched systems are not exploitable.
IBM i releases 7.3, 7.4, 7.5, and 7.6 contain an improper authentication weakness that lets a remote attacker who already holds valid IBM i credentials bypass intended security restrictions and read limited information they should not be able to access. The flaw is network-reachable with low attack complexity and no user interaction (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, score 4.3), but it cannot be triggered by an unauthenticated outsider, so realistic risk is confined to malicious insiders or attackers who have already obtained a low-privileged account. No public exploit code and no confirmed active exploitation have been identified at time of analysis, and IBM has published vendor-supplied fixes.
IBM i releases 7.3, 7.4, 7.5 and 7.6 can allow a remote authenticated attacker to slip past the ChrootDirectory confinement that is supposed to isolate SSH/SFTP users, exposing files and data outside the directory they were meant to be restricted to. The weakness is entirely dependent on configuration: it only affects systems that explicitly set ChrootDirectory in sshd_config and rely on it as an isolation boundary, while default deployments without chroot confinement are not impacted. No public exploit code has been identified at time of analysis, and because a valid restricted-account credential is mandatory and the assessed impact is bounded to low confidentiality and integrity loss with no availability effect, this rates as a moderate, operator-dependent issue rather than an emergency.
Denial of service in IBM i's Digital Certificate Manager (DCM) for System TLS allows a local, high-privileged attacker to prevent secure network connections from starting or cause fallback to non-secure connections. Affected versions are IBM i 7.3, 7.4, 7.5, and 7.6. No public exploit code or active exploitation has been identified at time of analysis, and the requirement for authenticated, high-privilege local access makes this a moderate-severity, low-urgency issue.
Improper verification of cryptographic signatures in IBM Db2 Genius Hub 1.0 allows local attackers to bypass JWT signature validation, leading to partial information disclosure and data integrity loss. The flaw requires local access (AV:L) with no authentication or user interaction, but its impact is limited to low confidentiality and integrity (C:L/I:L), making it a moderate-severity, lower-priority issue. No public exploit has been identified, and IBM has released a patch.
Missing initialization vector handling in IBM Db2 Genius Hub 1.0 allows a remote authenticated attacker holding low privileges to weaken the product's cryptographic protection and bypass security restrictions, resulting in a limited integrity impact. Exploitation is constrained by high attack complexity - the attacker must be able to observe or influence the affected ciphertext and benefit from favorable conditions such as repeated or predictable plaintext - and there is no confidentiality or availability impact. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the overall risk is low (CVSS 3.1 base score 3.1).
In the Linux kernel, the following vulnerability has been resolved: powerpc: Do not restore KUAP in arch_exit_to_user_mode_prepare() KUAP means kernel cannot touch user memory unless it explicitly is enabled. In the kernel it should stay AMR_KUAP_BLOCKED. While returning to userspace just before RFI, kernel should restore the user AMR value back. Looks like GENERIC_ENTRY might be treating arch_exit_to_user_mode_prepare() as the last architecture step before returning to userspace. commit bee25f97ad24 ("powerpc: Enable GENERIC_ENTRY feature") therefore called kuap_user_restore() from that hook. But on PowerPC that is too early. After irqentry_exit() / syscall_exit_to_user_mode() we still run platform specific exit routines. e.g. code snippets showing both exception handling and system call handling as the callers of function arch_exit_to_user_mode_prepare() which does kuap_user_restore(). The below path shows that calling kuap_user_restore() is too early when called from arch_exit_to_user_mode_prepare(). Exception handling in exceptions-64s.S ======================================= bl CFUNC(do_page_fault) ..DEFINE_INTERRUPT_HANDLER_ASYNC(do_page_fault) arch_interrupt_async_enter_prepare(regs); state = irqentry_enter(regs); instrumentation_begin(); irq_enter_rcu(); handler(regs); nap_adjust_return(regs); irq_exit_rcu(); instrumentation_end(); arch_interrupt_async_exit_prepare(regs); irqentry_exit(regs, state); <<< too early irqentry_exit_to_user_mode() __exit_to_user_mode_prepare(regs, EXIT_TO_USER_MODE_WORK_IRQ); arch_exit_to_user_mode_prepare(regs, ti_work); <<< too early b interrupt_return_srr .. bl CFUNC(interrupt_exit_user_prepare) <<< already calls kuap_user_restore prep_irq_for_enabled_exit() retry can run kernel code with IRQs on. So only when that routine is fully finished is when the user KUAP should be fully restored which interrupt_exit_user_prepare() already takes care of before returning. Similarly for system call handling in interrupt_64.S ====================================================== bl CFUNC(system_call_exception) .Lsyscall_exit: addi r4,r1,STACK_INT_FRAME_REGS li r5,0 /* !scv */ bl CFUNC(syscall_exit_prepare) .. kuap_assert_locked(); syscall_exit_to_user_mode(regs); <<< too early syscall_exit_to_user_mode_prepare(regs); <<< too early kuap_user_restore(regs); <<< already calls syscall_exit_prepare(), which can enable IRQs, replay a pending interrupt, and only then rfi. Those functions already restore KUAP immediately before rfi. Note that if we restore the user AMR too early like in the current code as shown from the code snippets above, then we get the following warning when CONFIG_PPC_KUAP_DEBUG is enabled: WARNING: arch/powerpc/include/asm/book3s/64/kup.h:293 at interrupt_exit_user_prepare+0x1a0/0x1c0 Hardware name: IBM pSeries (emulated by qemu) POWER10 (architected) TRAP: 0700 LR: c00000000000d8d4 CTR: c0000000021fe500 MSR: <SF,EE,ME,IR,DR,RI,LE> CR: 44000804 XER: 20040000 interrupt_exit_user_prepare+0x1a0/0x1c0 interrupt_return_srr_user+0x8/0x12c
Directory traversal in IBM WebSphere Application Server - Liberty (versions 17.0.0.3 through 26.0.0.9) lets a local, authenticated attacker who can deploy application archives write files outside the intended application directory by embedding crafted path entries in an archive. The attack is constrained rather than remote: the assessed vector is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N (5.5), meaning the attacker must already hold local access and application-deployment privileges, and the only impact is integrity (file write) with no confidentiality or availability loss. This is a moderate-severity, low-urgency issue rather than a top priority; no public exploit identified at time of analysis and no confirmed actively exploited (CISA KEV) status.
Man-in-the-middle interception of traffic from the IBM WebSphere Application Server - Liberty administrative client (versions 17.0.0.3 through 26.0.0.9) can expose sensitive information, because the client does not properly validate TLS certificates (CWE-295). The flaw is rated CVSS 6.5 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N): no authentication or user interaction is required, but exploitation demands that an attacker already occupy a position on the network path - a shared LAN segment, hostile Wi-Fi, compromised gateway or proxy, or an internal lateral foothold - making it a moderate-severity information-disclosure issue rather than a top-tier priority. There is no public exploit identified at time of analysis and the issue is not reported as confirmed actively exploited (CISA KEV); internet-only attackers with no interception capability cannot trigger it.
Information disclosure in IBM WebSphere Application Server - Liberty 17.0.0.3 through 26.0.0.9 lets an authenticated remote user retrieve sensitive server information when the restConnector-2.0 administrative feature is enabled. Rated CVSS 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), the issue requires valid credentials against the management interface and results in confidentiality loss only, with no integrity or availability impact; because restConnector-2.0 is not part of a minimal default Liberty server, deployments that never enabled it are not exposed. No public exploit code and no confirmed active exploitation were identified at time of analysis, making this a moderate-priority issue rather than an emergency.
Information disclosure in IBM WebSphere Application Server - Liberty (versions 17.0.0.3 through 26.0.0.9) lets a principal holding only the read-only Reader role send a crafted request to the version-information retrieval path and cause an uncaught exception, rooted in an integer overflow flaw (CWE-190), that exposes version data. Rated CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N), the impact is limited to low-sensitivity information disclosure with no stated effect on integrity or availability, and exploitation is not remote-unauthenticated - the attacker must already possess or have compromised a low-privilege authenticated account. No public exploit code and no CISA KEV entry were identified at the time of analysis.
Privilege escalation in IBM WebSphere Application Server Liberty (versions 17.0.0.3 through 26.0.0.9) allows an authenticated low-privileged user to bypass authorization checks and carry out management operations beyond their assigned role, but only on servers where the optional restConnector-2.0 feature has been explicitly enabled. It carries a medium CVSS 3.1 score of 5.4 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N) as a CWE-863 improper authorization flaw, meaning credentials are required, no user interaction is needed, and impact is limited to low confidentiality and integrity loss with no availability impact. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and the exposure is meaningfully limited because a bare default server.xml does not enable this connector.
Stored cross-site scripting in IBM's MCP Context Forge (versions 0.2.0 up to but not including 0.3.1) lets an authenticated user who can create or save a Global Prompt store markup with script-capable event handlers, which then executes in the browser of any other user who views that saved prompt in the MCP Admin UI. Successful exploitation can rewrite the interface, display phishing content, capture keystrokes reachable by the page, and perform actions with the victim's browser session, but it requires a valid account, an enabled Admin UI, and a second user to open the prompt. There is no public exploit identified at time of analysis, no KEV listing, and the vendor-released patch in version 0.3.1 (commit acd1619, PR #337) also flips MCPGATEWAY_UI_ENABLED and MCPGATEWAY_ADMIN_API_ENABLED to false by default, removing the surface entirely for patched deployments.
Improper access control in IBM i 7.3, 7.4, 7.5, and 7.6 allows a local attacker who already holds a valid account on the system to trigger a denial-of-service condition, while the supplied impact metrics also point to a low-severity information exposure. The issue carries a moderate CVSS score of 5.3, and there is no CISA KEV listing, no EPSS score provided, and no public exploit code identified at time of analysis, so this should be treated as a low-urgency, locally-privileged defect rather than an active threat. Defenders should note that the published vector (AV:N/PR:N, C:L, A:N) contradicts both IBM's own 'local attacker' description and our assessed vector (AV:L/PR:L), and also fails to express an availability impact despite the denial-of-service wording - this is a data-quality conflict that should be resolved with IBM before assuming network-facing exposure.
User profile enumeration in IBM i 7.3, 7.4, 7.5, and 7.6 allows unauthenticated remote attackers to determine which user profiles exist by observing distinct error codes returned during the sign-on process. The issue requires only network reachability to an exposed IBM i sign-on interface - no credentials and no user interaction (CVSS 3.1 base 5.3, AV:N/AC:L/PR:N/UI:N, C:L only) - and yields nothing beyond confirmation of valid profile names, so it is a reconnaissance weakness rather than a compromise vector. No public exploit code has been identified at time of analysis, the vulnerability is not listed in CISA KEV, and IBM has published a fix.
Brute-force credential guessing against IBM i authentication interfaces can let remote attackers recover valid user credentials, because the platform fails to sufficiently restrict repeated authentication attempts. IBM i releases 7.3, 7.4, 7.5, and 7.6 are affected, and exploitation is unauthenticated (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, base score 5.3), requiring only network reachability to an exposed sign-on endpoint and an account whose password is weak enough to be guessed. This is a moderate-severity weakness rather than a remote code execution or integrity-impacting flaw; no public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV, though any organization exposing IBM i authentication services to untrusted networks should prioritize the vendor fix and tighten lockout and rate-limiting controls.
Local users on IBM i 7.3, 7.4, 7.5, and 7.6 can modify the system BOOTP table because the operating system fails to enforce a proper authority check on that configuration function, a case of improper privilege management (CWE-269). Exploitation requires an interactive or authenticated local presence on the host with at least low-level privileges (CVSS vector AV:L/PR:L), so neither a remote nor a fully unauthenticated attacker can trigger it, and the resulting impact is capped at low confidentiality and low integrity with no availability effect (CVSS 4.4). No public exploit code has been identified at time of analysis and there is no evidence of active exploitation, though IBM has published a vendor fix; this is a low-to-moderate priority issue rather than a top-tier emergency, with exposure scaling with the number of local accounts permitted on the partition.
Cross-site scripting in IBM i 7.3, 7.4, 7.5, and 7.6 allows an authenticated remote user to inject arbitrary script into content that is later rendered by another user's browser, because user-supplied input is not properly validated before being included in a page. Exploitation is not automatic: an attacker must already hold an authenticated session on the system and a separate victim must view or interact with the injected output, so this is not a default-configuration, unauthenticated remote exploit. IBM has published a fix through its support portal, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Exposure of JavaScript source map files in IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 lets remote attackers retrieve the original, unminified client-side source of the web application, exposing internal identifiers, endpoint references, comments and other development-time detail. Per the assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) no authentication or user interaction is required, and the impact is confined to a low-severity confidentiality loss - reconnaissance material rather than direct access, since integrity and availability are unaffected. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and EPSS data was not provided; the vendor itself scored the attack vector as adjacent (AV:A), which would further limit exposure to attackers on the same local or logical network segment. This is a low-priority finding that is nonetheless a confirmed, genuinely disclosed product weakness.
Local information disclosure in IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 allows an attacker who already has access to the host to read sensitive data by abusing a service account that was configured with excessive permissions. The flaw is a privilege-assignment problem (CWE-250) rather than a memory-safety or injection bug: because the service account holds rights beyond what it needs, anything reachable by that account - files, directories, or configuration - becomes reachable to a local user. Impact is confidentiality-only (C:H with I:N/A:N on CVSS 3.1, base 6.2, AV:L/AC:L/PR:N/UI:N), so no tampering or denial of service is involved, there is no network attack path, and there is no public exploit identified at time of analysis; IBM has published a fix referenced in advisory node/7291755.
Cleartext transmission of sensitive information in IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 can allow a local attacker who can observe the relevant channel to obtain limited sensitive information. The assessed vector is CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, meaning exploitation requires local access and no authentication or user interaction but only affects confidentiality; the CVE record lists a base score of 5.1. No public exploit identified at time of analysis, and a vendor patch is available per IBM's advisory.
Stored cross-site scripting in IBM Planning Analytics 2.0 and 2.1 allows an authenticated user holding a valid account on the Web UI to persist arbitrary JavaScript into a stored field, which then executes in the browser of any other user who views that content - potentially disclosing credentials or session data within a trusted session. Per the assessed vector (CVSS 6.4, AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N), exploitation requires both the attacker's existing authenticated access and a second victim user viewing the affected page, and impact is bounded to low confidentiality and integrity within the browser session rather than server-side code execution or availability loss. There is no public exploit code, no CISA KEV listing, and no EPSS score in the available intelligence, so the flaw rates as 'no public exploit identified at time of analysis'.
Cross-site scripting in IBM Planning Analytics 2.0 and 2.1 allows remote attackers to execute arbitrary JavaScript in a victim's browser session by supplying content that is rendered without proper output encoding. Per the supplied CVSS vector (AV:N/AC:L/UI:R/S:U/C:L/I:L/A:N, base 5.4), exploitation requires the victim to interact with or load the attacker-influenced page, and impact is confined to that user's browser context rather than the underlying host or other accounts. No public exploit identified at time of analysis, and no exploitation activity is recorded in CISA KEV; patch available per vendor advisory. Note that the vector's PR:N conflicts with IBM's description of a 'remote authenticated attacker', so authentication requirements are not confirmed from available data and should be verified against IBM support node 7291604.
IBM DataStage on Cloud Pak for Data 5.4.0.0 exposes sensitive information to users who are not authorized to see it, letting an attacker who already holds a valid low-privilege account read data outside their intended scope over the network with no user interaction and low attack complexity. The independent assessment rates the flaw as confidentiality-only (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), so integrity and availability are not affected and the practical limiting factor is the requirement for authenticated access plus network reachability of the Cloud Pak for Data instance - this is not an anonymous, pre-authentication attack. The one caveat worth flagging is that IBM's own vector (9.6, S:C/I:H/I:H) asserts scope change and integrity impact that our assessment does not corroborate from the advisory text; there is no public exploit code and no CISA KEV entry, so there is no public exploit identified at time of analysis, and IBM has published a vendor advisory with patch guidance.
Local information disclosure in Code for IBM i (the codefori/vscode-ibmi Visual Studio Code extension) before 3.0.1 lets other local accounts on the same host read sensitive content written to the shared /tmp directory during Object Browser downloads and the edit-save workflow, because those files are not reliably cleaned up after use. Although the vendor scored it 5.1 on a CVSS:4.0 vector carrying AV:N, exploitation in practice requires an attacker who already holds a separate local account on a shared multi-user machine with a readable /tmp (a common default on many Unix/Linux systems) plus a legitimate developer having performed a download or edit-save in a vulnerable version; single-user workstations and hosts with per-user private temp directories are not affected. Our independent assessment rates it CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N - a low-to-medium risk, confidentiality-only issue - and there is no public exploit identified at time of analysis.
Code injection in IBM Maximo Application Suite's Location Service for Esri component (versions 9.0, 9.1, and 9.2) allows an authenticated attacker with high privileges (CVSS PR:H) and network access to supply an unsanitised container image configuration in the Kubernetes operator template, which the operator may then deploy. The issue is rated CVSS 6.5 Medium (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N) and can lead to high confidentiality and integrity impact, but requires privileged access to the MAS environment and affects an optional component. No public exploit identified at time of analysis, and no KEV or EPSS data indicates active exploitation.
Connection-resource exhaustion in IBM Power Systems firmware levels FW1110.00 through FW1110.31, FW1120.00 through FW1120.01, and FW1060.00 through FW1060.81 lets a highly privileged attacker on an adjacent network segment drive a denial of service by consuming connections the service processor never releases, until legitimate management traffic can no longer be serviced. The assessed vector (CVSS 4.5, AV:A/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H) means exploitation requires pre-existing administrative access to the affected interface plus network adjacency to the management segment, which confines realistic risk to insiders or attackers who have already established a foothold on the management network; confidentiality and integrity are unaffected. No public exploit has been identified at time of analysis and there is no indication of active exploitation, making this a low-to-moderate priority availability issue rather than an urgent one.
Improper input validation in IBM Db2 11.5.0 through 11.5.9 and 12.1.0 through 12.1.5 lets a local attacker who already holds authenticated low-privilege access to the database host or instance disrupt the affected component, resulting in a limited availability impact. The issue is not remotely reachable and cannot be triggered by an unauthenticated user; our assessment rates it CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L, a low-severity availability-only condition, and there is no public exploit identified at time of analysis. Overall this is a low-priority, low-real-risk issue despite being a named CVE, and vendor patching is available.
Denial of service in IBM Db2 11.5.0 through 11.5.9 and 12.1.0 through 12.1.5 can be triggered by an authenticated, low-privileged user (PR:L) submitting a specially crafted query that references a Materialized Query Table, causing a stack-based buffer overflow (CWE-121) that crashes the database engine. IBM has released a patch; no public exploit identified at time of analysis, and impact is limited to availability with no data disclosure or modification. Note that IBM's CVSS vector indicates local access (AV:L), while the query-execution nature suggests a remote authenticated client may be able to trigger the flaw, pending confirmation with the vendor.
Reflected cross-site scripting in IBM DB2 Recovery Expert for Linux, UNIX and Windows 5.5 IF 2 lets an unauthenticated attacker inject arbitrary JavaScript into the product's Web UI, which then executes in the browser of a logged-in user within a trusted session and can lead to credential or session disclosure. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N, score 6.1) shows the attacker does not need to authenticate, but a victim with an active session must be induced to trigger the reflected payload, making user interaction the primary limiting factor and the practical risk moderate-to-low. No public exploit code or confirmed active exploitation has been identified at time of analysis, and a vendor patch is available (CWE-79).
Reflected cross-site scripting in IBM Db2 Recovery Expert for Linux, UNIX and Windows 5.5 IF 2 allows an unauthenticated attacker to embed arbitrary JavaScript in the Web UI, which executes in the browser of a victim operator who interacts with the crafted content and can lead to disclosure of credentials from a trusted session. The flaw is rated CVSS 6.1 (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N), meaning no attacker authentication is needed but the payload only fires after a legitimate user opens or interacts with the injected content, so this is not a drive-by, self-propagating compromise. Exploitation status is assessed as no public exploit identified at time of analysis, with no CISA KEV listing; the practical exposure is limited by the mandatory user interaction, the narrow deployment base of this recovery tooling, and the fact that only the specific 5.5 IF 2 build is in scope.
Reflected cross-site scripting in IBM Db2 Recovery Expert for Linux, UNIX and Windows 5.5 IF 2 Web UI allows unauthenticated remote attackers to inject arbitrary JavaScript into a victim's trusted session, potentially leading to credential disclosure. The CVSS 3.1 base score is 6.1 (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N); no public exploit was identified at time of analysis. A vendor patch is available, and successful exploitation requires a logged-in operator to interact with attacker-supplied input.
Untrusted external web-link handling in IBM Db2 Recovery Expert for Linux, UNIX and Windows 5.5 Interim Fix 2 allows a remote, unauthenticated attacker to craft a link that can expose sensitive information or trigger unauthorized actions inside a victim's browser (CWE-1022). The flaw cannot be triggered server-side or automatically: it requires the victim to click an attacker-supplied link that resolves through the application's untrusted external reference, so the practical barrier is social engineering rather than authentication (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N, score 6.1). Impact is confined to the victim's browser context rather than the Db2 Recovery Expert host, and no public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis.
Denial of service in IBM Db2 11.5.0 through 11.5.9 and 12.1.0 through 12.1.5 can be triggered by an authenticated user who holds INSERT privileges on a table containing one or more XML columns, potentially crashing or hanging the database instance under conditions IBM has not fully quantified. The flaw is classified as uncontrolled resource consumption (CWE-770) and carries a CVSS 3.1 score of 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), meaning the impact is confined to availability with no confidentiality or integrity loss. Exploitation requires a valid Db2 session (PR:L) and typical SQL INSERT access, but no public exploit code has been identified at time of analysis and there is no indication of active exploitation; this is a moderate-priority availability issue rather than a critical emergency. Vendor patches are available per IBM's advisory.
Local privilege escalation in IBM Db2 11.5.0-11.5.9 and 12.1.0-12.1.5 allows an authenticated low-privileged user on the database host to abuse the db2pd monitoring and diagnostic utility to gain privileges beyond those they legitimately hold. Exploitation requires pre-existing local shell access and the ability to run db2pd, so the flaw is not reachable remotely or by unauthenticated actors; it matters most on shared, multi-tenant, or otherwise privileged-access Db2 servers. Our independent assessment rates the true impact higher than IBM's published CVSS 6.5, scoring it CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H; no public exploit code has been identified and the issue is not confirmed as actively exploited (not in CISA KEV), though a vendor patch is available and should be applied to remove the condition.
Denial of service in IBM Guardium Data Protection 12.2.2 allows remote unauthenticated attackers to degrade availability by racing concurrent unsynchronized writes to a shared map. The supplied CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 7.5) describes availability-only impact with no confidentiality or integrity loss; our assessment refines attack complexity to AC:H because the non-deterministic race window reduces reliability below AC:L. No public exploit identified at time of analysis, and a vendor patch is available via IBM Support node 7288627, so patched or non-12.2.2 deployments are not exposed.
Denial of service in IBM Guardium Data Protection 12.2 is achievable by an authenticated remote attacker using path traversal sequences against a network-reachable component, with high integrity and availability impact (CVSS 3.1 base 8.1). The CVSS vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H confirms the attacker needs only low-privilege credentials, no user interaction, and low attack complexity, so the main barrier is obtaining a valid Guardium account. No public exploit identified at time of analysis, and the supplied data does not confirm active exploitation or CISA KEV listing.
Cleartext storage of sensitive information in IBM Guardium Data Protection 12.0, 12.1, and 12.2 application logs allows a local, authenticated low-privileged user with read access to those log files to obtain limited sensitive data (CWE-532). IBM rates this at a CVSS 3.1 base score of 3.1, but the network attack vector in the vendor vector overstates real-world reachability: exploitation depends on an existing local foothold on the appliance and on sensitive values being written to logs only intermittently or conditionally, so impact is confined to limited confidentiality disclosure with no integrity or availability effect. There is no public exploit identified at time of analysis, and a vendor patch is available.
High-privileged, already-authenticated administrators on the management interface of IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 can forge or tamper with audit log records by injecting argument delimiters into the logging functionality (CWE-88). Because the CVSS vector is PR:H, only an account that already holds elevated privileges on the management console can reach the affected feature, so realistic exposure is confined to insider misuse or an attacker who has already stolen a privileged credential; no user interaction is required and the interface is network-reachable, but impact is limited to audit log integrity with no confidentiality or availability effect. There is no vendor indication of exploitation, and no public exploit identified at time of analysis; severity is low (CVSS 2.7), and a patch is available per the vendor advisory.
SQL injection (CWE-89) in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 allows a remote attacker holding a valid low-privileged session to inject SQL through standard authenticated functionality, enabling unauthorized modification of backend data and partial denial of service. The vendor-assigned CVSS 3.1 score is 5.4 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L), so confidentiality is not assessed as impacted; the practical barrier is the requirement for credentials, not a special configuration. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and IBM has published a fix via its support portal.
Cross-site scripting (CWE-79) in the Web UI of IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 - including their container editions - lets an attacker inject arbitrary JavaScript into pages rendered by the interface, which can execute in the browser of an authenticated administrator or operator with an active trusted session and potentially disclose credentials or session data. The injection itself requires no authentication (the supplied vector is PR:N), but the payload is only harmful when a victim loads the crafted content (UI:R), so exploitation depends on a successful lure, a poisoned page, or injection into a view the victim already opens. IBM rates this 8.2 (scope changed, high confidentiality and integrity impact); no public exploit code or active exploitation has been identified at time of analysis, though the faulted UI is a high-value administrative target. Note a vector discrepancy: the published CVSS marks AV:L whereas the independent assessment scores AV:N, so defenders should confirm with IBM whether the affected UI is reachable remotely or only from a local/management network, since that materially changes exposure.
Security restriction bypass in IBM Security Verify Access (10.0 through 10.0.9.2) and IBM Verify Identity Access (11.0 through 11.0.3), including their container images, lets a remote attacker who already holds a valid low-privilege session circumvent authentication controls and gain high confidentiality and integrity impact (CVSS 3.1 base 8.1, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N). Because the vector is PR:L, anonymous or unauthenticated attackers cannot trigger this on their own; the attacker must first possess valid credentials or a session, after which the bypass is low-complexity, requires no user interaction, and is reliably reproducible. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (no CISA KEV listing), but a vendor patch is available, so the issue should be treated as a credible, above-average-priority fix rather than an emergency.
An authenticated user can exhaust server resources in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3, including the containerized editions, by submitting a specially crafted HTTP query that triggers uncontrolled resource allocation, resulting in a denial of service (CVSS 3.1 base 6.5, AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H). Exploitation requires a valid authenticated session on the affected HTTP interface (PR:L); there is no confidentiality or integrity impact, only availability. No public exploit code was identified at time of analysis and the issue is not listed in CISA KEV, so this is a moderate-priority availability defect rather than a top-tier emergency; vendor patching is available per IBM's advisory.
Authentication workflow bypass in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 allows a remote authenticated attacker who already holds valid first-factor credentials or an active session to skip the configured additional authentication workflow steps - such as step-up authentication, multi-factor prompts, or multi-step policy flows. Rated CVSS 6.5 (moderate), the flaw only affects deployments that actually enforce an additional authentication workflow; environments without one have nothing for the bypass to defeat. Exploitation requires the extra-workflow feature to be configured and the attacker to be a remote authenticated actor, and no public exploit code or confirmed in-the-wild exploitation has been identified at time of analysis; note that IBM's supplied CVSS vector (PR:N) contradicts its own 'remote authenticated attacker' description and our independent assessment, which uses PR:L and should be reconciled with the vendor.
A remote, unauthenticated attacker can trigger a limited heap-based out-of-bounds read in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3, including their container editions, by sending a specially crafted request to an exposed instance. Successful exploitation is confined to a partial memory read that can cause a denial-of-service condition; there is no confidentiality or integrity impact and no code execution path described. This is a low-severity issue (CVSS 3.1 base 3.7, AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L) that should be treated as low priority despite its network-facing nature, and at time of analysis no public exploit code and no confirmed active exploitation were identified; a vendor patch is available via IBM support node 7291628.
Authenticated cross-site scripting (XSS) in the local management interface of IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 allows a low-privileged authenticated user to embed arbitrary JavaScript into the Web UI when the deployment is in certain non-default configurations, potentially altering the interface's intended behaviour and disclosing credentials within a trusted session. Exploitation requires an existing account on the management interface (CVSS PR:L) and, in practice, a second trusted user such as an administrator who renders the injected content in their own session; no public exploit code and no confirmed active exploitation were identified at time of analysis. The issue is rated low-to-moderate priority - network-reachable but gated by high attack complexity (AC:H) attributable to the configuration prerequisite and by user interaction in the assessed vector.
Cross-site scripting in the IBM Security Verify Access (10.0 through 10.0.9.2) and IBM Verify Identity Access (11.0 through 11.0.3) Web UI allows an authenticated user to embed arbitrary JavaScript into a field that is later rendered to another user, so the payload executes within that victim's trusted session (scope change, S:C) and can lead to credential or session disclosure. The CVSS vector (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N, score 5.4) confirms remote reachability but requires a valid low-privileged account plus victim interaction; there is no availability impact and the exposure is limited to data reachable inside the victim's session. No public exploit code exists and there is no confirmed active exploitation (CISA KEV) at the time of analysis; a vendor patch is available per the IBM advisory.
Stored cross-site scripting in IBM Guardium Data Protection 12.2 lets an unauthenticated attacker who can influence traffic on a database that Guardium monitors plant a malicious script that later executes in the browser of a logged-in Guardium operator when the Quick Search results grid renders the stored payload (CWE-79). IBM rates this CVSS 9.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N), but an independent reassessment places it at CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N because the victim must actively open the Quick Search grid and hold an authenticated, privileged console session - a real limiting factor the vendor's UI:N rating does not capture. Exploitation therefore requires two conditions together: attacker-controlled data must reach the monitored database traffic Guardium ingests, and a Guardium user must subsequently view those results; no public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV).
IBM Guardium Data Protection 12.2.2 writes SECRET and API_KEY credential material into INFO-level logs produced by the edge-controller and edge-manager components during credential rotation, so an authenticated attacker who can read those application or container logs can harvest live service credentials and later use them to impersonate services or reach the Guardium control plane. Exploitation requires prior Guardium authentication (the vector carries PR:L), read access to the affected logs, and that a rotation event occur or be induced so the secret is actually written; no user interaction is involved. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the vendor advisory (IBM support node 7288627) is the primary reference. Because the prerequisite is log readability on the host or container rather than open network reachability, our assessment treats the vector as local (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) even though the vendor scores it AV:N.
IBM Guardium Data Protection 12.0, 12.1 and 12.2 ship the WfpMonitor kernel driver, whose METHOD_NEITHER IOCTL handlers dereference caller-supplied pointers without consistent probing or exception handling, so a local attacker who already holds high privileges on the host can trigger a system crash or obtain limited reads of kernel memory. The CVSS 3.1 vector (AV:L/PR:H/UI:N, C:L/I:N/A:H, score 5.1) confirms the flaw is local-only and requires pre-existing elevated privileges, meaning it grants no privilege escalation and has no integrity or code-execution impact. There is no CISA KEV entry and no public exploit code identified at time of analysis, and a vendor patch is available, making this a moderate-to-low real-world priority that is best handled through routine driver patching.
Signature forgery in IBM DataPower Gateway lets an authenticated user with valid low-privilege credentials submit signature requests that the appliance processes without properly verifying data authenticity, producing forged signatures that relying parties may accept as genuine. Affected firmware spans 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2; the impact is integrity-only (CVSS 3.1 base 6.5, AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N) with no confidentiality or availability loss. There is no public exploit identified at time of analysis, and IBM has published a vendor fix via its support portal, so this is a moderate-risk authenticated integrity issue rather than a remotely exploitable, unauthenticated critical defect.
Stored/reflected cross-site scripting in the administrative Web UI of IBM DataPower Gateway (10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2) lets an authenticated user whose input is rendered back into UI pages embed arbitrary JavaScript that executes in the browser of another, potentially more-privileged user, enabling credential or session disclosure inside the trusted management session. The flaw is not self-executing: it requires a low-privileged authenticated position (PR:L) plus a second victim who views the injected content (UI:R), and there is no public exploit identified at time of analysis, nor is it listed in CISA KEV. At CVSS 5.4 (CWE-79) this is a genuine but non-urgent issue, with realistic risk confined to deployments whose management Web UI is reachable by multiple users of differing privilege levels.
Improper authorization in IBM DataPower Gateway lets a local attacker who already holds a valid low-privileged account read sensitive information that should be restricted from that privilege level. Exposure is limited to specific builds: 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6 (10.6CD), and 11.0.0.0 through 11.0.0.2. Exploitation requires local access to the appliance plus authenticated credentials (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N), so realistic risk is confined to insiders or post-compromise scenarios; CISA SSVC records no known exploitation, no public exploit code is identified at time of analysis, and IBM has published a vendor patch (support node 7289775).
Denial of service in IBM DataPower Gateway (10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2) allows a remote unauthenticated attacker to degrade or stall request processing by submitting input that forces worst-case algorithmic complexity during linked-list traversal. Rated CVSS 5.9 (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H), the flaw is an availability-only issue: the CVSS AC:H rating reflects that the attacker must craft input to hit the pathological code path rather than simply flooding the gateway with arbitrary traffic, and impact is confined to service degradation or denial with no confidentiality or integrity effect. No public exploit identified at time of analysis, and a vendor patch is available.
Denial of service affecting IBM DataPower Gateway builds 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2, where a crafted GraphQL request containing a malformed variable causes a NULL pointer dereference that crashes or hangs the affected service. The flaw is network-reachable and requires no authentication (PR:N) and no user interaction (UI:N), but the HIGH attack complexity (AC:H) means the attacker must craft input that reliably reaches the dereference, so opportunistic mass exploitation is unlikely. Impact is availability-only with no data disclosure or modification, and no public exploit identified at time of analysis; this is a moderate, availability-only issue rather than a top-tier priority.
An out-of-bounds read in IBM DataPower Gateway (CWE-125) lets an attacker who already holds valid credentials on the gateway reach past intended buffer boundaries and have fragments of process memory returned to them, disclosing limited sensitive information. Affected release trains are 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2, as listed in ENISA EUVD-2026-94890 and IBM's advisory node/7289775. The base score is 5.3 with confidentiality-only, low-severity impact and no effect on integrity or availability; IBM's description requires a remote authenticated user, which the independent assessment reflects by treating the vector as PR:L instead of NVD's PR:N. No public exploit code has been identified at time of analysis and there is no CISA KEV entry, so realistic risk is confined to credentialed actors and compromised accounts rather than unauthenticated mass exploitation.
Server-side request forgery in IBM DataPower Gateway (10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2) lets an authenticated user who satisfies high-complexity preconditions make the appliance send requests to destinations of the attacker's choosing, enabling internal network enumeration and reconnaissance that can support follow-on attacks. Rated CVSS 4.9 (AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N), this is a moderate-severity, low-priority issue rather than an emergency: exploitation requires a valid authenticated session plus the ability to reach a request-handling function that accepts an attacker-influenced destination, and there is no public exploit identified at time of analysis, with real-world impact bounded by whatever sensitive internal hosts the gateway itself can reach. IBM has published an advisory covering these builds, and other versions are not in scope.
Path traversal in IBM Langflow OSS 1.0.0 through 1.12.2 lets a remote attacker who holds a valid Langflow account read files outside the intended restricted directory, exposing sensitive data at high confidentiality impact (CVSS 6.5, CWE-22). The flaw is network-reachable, low-complexity and requires no victim interaction, but it cannot be triggered anonymously: the CVSS vector (PR:L) means the attacker must already be able to authenticate to the instance, so risk concentrates on internet-exposed or multi-tenant deployments with loose account provisioning. IBM has published a vendor patch (referenced in its support advisory), and no public exploit code was identified at time of analysis; no KEV listing was provided in the intelligence for this CVE.
Information disclosure in IBM Langflow OSS 1.0.0 through 1.12.2 allows a remote, authenticated attacker holding only low-privilege credentials to obtain sensitive information that should not be reachable from their account, resulting in a high confidentiality impact with no effect on integrity or availability. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N) confirms credentials are required and that no user interaction is needed, while the scope-change metric indicates the exposed data can affect resources beyond the vulnerable component itself. Patch available per vendor advisory; no public exploit identified at time of analysis, and no CISA KEV or EPSS signal was provided. This is a credible mid-tier priority rather than an emergency, and the practical risk hinges on how many low-privilege accounts exist and whether the instance is reachable from untrusted networks.
Authenticated users of IBM Langflow OSS 1.0.0 through 1.12.2 can exhaust server resources by supplying a crafted ZIP archive to a code path that performs extraction, degrading or halting availability of the affected instance (CVSS 3.1 base 4.3, CWE-400). The flaw is reachable over the network by a low-privilege authenticated attacker (AV:N/PR:L/UI:N) and is limited to availability impact (C:N/I:N/A:L), with no data exposure, integrity loss, or code execution demonstrated. This is a low-to-moderate priority issue, not an urgent one: it is not confirmed as actively exploited (no CISA KEV listing) and no public exploit code has been identified at time of analysis, though the mandatory credential requirement means exposure is confined to deployments with reachable ZIP-extraction functionality.
Path traversal in IBM Langflow OSS 1.0.0 through 1.12.2 allows an authenticated remote attacker to read files outside the intended directory, causing high-impact confidentiality loss (CVSS 6.5, C:H/I:N/A:N) without modifying data or disrupting service. Exploitation requires low-privileged credentials (PR:L) but is network-reachable, low-complexity, and needs no user interaction, so multi-tenant or self-registration deployments face elevated risk because obtaining an account is trivial; the flaw is a moderate-severity information-disclosure issue with middle-tier real-world priority. No public exploit code or confirmed active exploitation is identified at time of analysis, and IBM has published a vendor patch advisory.