Information Disclosure
Monthly
SELinux label manipulation via TOCTOU race condition in the policycoreutils fixfiles script allows a local low-privileged attacker to corrupt SELinux mandatory access control labels on arbitrary system files, including security-critical targets such as /etc/shadow. The flaw affects fixfiles when run in relabel or restore mode across all supported Red Hat Enterprise Linux releases (6 through 10), Red Hat Hardened Images, and OpenShift Container Platform 4. No public exploit code or active exploitation has been identified at time of analysis, and exploitation is constrained by both a required race condition win and the need for an administrator to actively invoke fixfiles.
TLS credential exposure in ZTE ZXHN F680 fiber gateway firmware allows an adjacent-network attacker to extract unencrypted cryptographic key material - classified under CWE-321 (Use of Hard-coded Cryptographic Key) - enabling potential decryption or impersonation of TLS-protected communications between the device and upstream ISP services. Seven discrete firmware versions are confirmed affected per the ENISA EUVD entry and ZTE's own advisory. No public exploit code or CISA KEV listing is confirmed at time of analysis, and the CVSS adjacency requirement and high complexity rating limit realistic exploitation to technically capable actors with local network proximity.
Root password hash exposure in ZTE F689 firmware allows a physical attacker to extract credential material stored in cleartext or weakly protected form within the device firmware image. The F689 is an ISP-deployed broadband gateway, and this vulnerability (CWE-916) means the hash protecting root-level access uses insufficient computational effort, making offline cracking feasible once extracted. No public exploit code has been identified and no active exploitation is confirmed; however, successful hash recovery grants an attacker a path to persistent root-level device compromise.
Out-of-Bounds Read in Autodesk's image handling library crashes Revit and AutoCAD when a user opens a maliciously crafted TIF file during image import. Affected products span Revit 2024, 2026, and 2027 as well as AutoCAD and AutoCAD LT 2027, all below vendor-specified fix versions. The attack is local and requires user interaction, limiting automated mass exploitation, but remains a viable denial-of-service vector in targeted scenarios against AEC professionals who routinely handle externally sourced CAD assets. No public exploit identified at time of analysis.
Reverse tabnabbing in PILOS versions 2.1.0 through 4.14.1 exposes authenticated users to session hijacking via phishing by omitting the Cross-Origin-Opener-Policy (COOP) response header on pages that open links in new browser tabs. When an authenticated user clicks a target="_blank" link within PILOS, the newly opened page retains a live window.opener reference to the original PILOS tab, allowing the destination page to silently redirect that tab to an attacker-controlled site mimicking PILOS login. No public exploit has been identified at time of analysis, and the vendor-confirmed fix is available in v4.14.1.
Uninitialized heap memory disclosure in FFmpeg's native TIFF decoder (libavcodec/tiff.c) exposes stale heap contents to any party able to retrieve decoded image output. Affected versions span 0.5 through 8.x; FFmpeg 9.0 carries the upstream fix. In server-side media pipelines that accept and return processed TIFF files - transcoding APIs, thumbnail generators, upload handlers - an attacker can craft a structurally valid Deflate-compressed TIFF strip that inflates short, causing the decoder to embed prior heap allocation remnants into the decoded output, potentially leaking sensitive in-process data. No active exploitation is confirmed (not in CISA KEV) and no standalone public exploit code was identified at time of analysis.
Uninitialized heap memory read in FFmpeg's native Screenpresso decoder (libavcodec/screenpresso.c) allows an attacker who can supply crafted SPV1-encoded video to recover stale heap contents - including userspace addresses and prior-frame data - from the process decoding the media. Affected versions span FFmpeg 3.0 through 8.x; version 9.0 resolves the issue via upstream commits and PR #23896. No active exploitation is confirmed in CISA KEV, and no public exploit code has been identified at time of analysis, but the information-disclosure primitive is particularly dangerous in persistent server-side decoding pipelines where heap residue from earlier operations may include sensitive material.
Heap memory disclosure in FFmpeg's native RSCC decoder (libavcodec/rscc.c) allows an attacker who can supply a crafted video file to expose residual heap contents - including data from prior heap allocations or previously decoded frames - to any downstream consumer of the decoded output. The flaw stems from rscc_decode_frame() calling av_image_copy_plane() without verifying that the number of decompressed bytes matches the declared tile geometry, allowing the unwritten suffix of the persistent ctx->inflated_buf to propagate silently into the output frame. All FFmpeg builds from 3.0 through 8.x are affected; no public exploit has been identified at time of analysis, and no KEV listing exists.
In the Linux kernel, the following vulnerability has been resolved: x86/bugs: Make Safe-RET robust against interrupt injection An attacker injecting interrupts while the Safe-RET mitigation executes on machines affected by SRSO can neutralize the safe return sequence, potentially leading to data leakage through speculative execution. Fixup register state as if the Safe-RET sequence executed successfully by "emulating" it, in a manner of speaking, and avoid executing a RET instruction after returning from the interrupt.
Terminal escape sequence injection in GitHub CLI (gh) prior to version 2.97.0 allows an attacker who controls content on GitHub - gists, pull requests, releases, codespaces, API responses, skills, or agent-task output - to embed ANSI/VT escape sequences that are rendered verbatim by the victim's terminal when they run any of the affected display commands. Impact ranges from cosmetic screen manipulation (title bar spoofing, on-screen content overwrite) to, on certain terminal emulators that interpret shell-integration or hyperlink escape sequences, arbitrary command execution in the user's shell. This issue broadens the same CWE-150 class addressed by CVE-2026-45803, which patched only the `gh run view --log` path, to the full set of content-displaying subcommands. No public exploit or KEV listing is present at time of analysis, though the injection surface is wide and the fix is confirmed in v2.97.0.
GitHub CLI's `gh auth status` command in versions prior to 2.97.0 partially exposed fine-grained personal access tokens and GitHub App tokens in terminal and CI output due to a flawed masking algorithm. The defect used `strings.LastIndexByte` to find the last underscore as the masking boundary - for tokens like `github_pat_APPID_secretbody` or `ghs_APPID_JWT`, this left the middle segment (between the type prefix and the last underscore) visible in plain text. Affected token types include fine-grained PATs (`github_pat_*`), GitHub App installation tokens (`ghs_*`), user access tokens (`ghu_*`), and the Actions `GITHUB_TOKEN`; classic tokens (`gho_*`, `ghp_*`) are not affected. No public exploit is identified at time of analysis.
Session cookie theft in the DataPress (Dataverse Integration) WordPress plugin before 2.91 allows any Contributor-level user to steal session credentials from higher-privileged users such as Editors or Administrators. The plugin's template rendering feature improperly exposes the session data of users who view affected content, enabling privilege escalation via session hijacking. No public exploit code has been identified at time of analysis, but the low barrier to entry (Contributor role) makes this a realistic insider or compromised-low-privilege-account threat against WordPress sites using this plugin.
Unauthenticated information disclosure in OpenReception appointment-booking-software prior to version 1.0.5 exposes private channel metadata through the public `/api/tenants/{id}/schedule` endpoint, bypassing the `isPublic` flag that governs channel visibility in the booking UI. Any caller with a valid tenant ID can retrieve channel names, descriptions, IDs, agent associations, pause status, confirmation requirements, and computed slot availability for channels deliberately configured as internal-only - data that the product's own design intends to hide from public callers. No public exploit has been identified and the vulnerability is not listed in CISA KEV, but the CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms trivial unauthenticated reachability requiring no special conditions.
Out-of-bounds heap read in llama.cpp's recurrent memory state restore path (builds b5702 through b7653) allows an attacker with write access to the slot save directory to craft a malicious slot file that triggers heap data leakage - including pointer values - into server logs, effectively defeating ASLR protections and enabling multi-stage exploitation. No public exploit has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalogue. An upstream fix is available as a commit to the ggml-org/llama.cpp repository, though a tagged released version past the affected build range has not been independently confirmed.
Cross-origin data leakage in Google Chrome's GPU process - caused by an integer overflow (CWE-190) - enables a remote attacker who has already achieved renderer process compromise to read data across origin boundaries by delivering a crafted HTML page. All Chrome desktop releases prior to 151.0.7922.109 are affected. No public exploit or CISA KEV listing exists at time of analysis; the chained nature of the attack (requiring a prior renderer compromise) substantially constrains real-world risk despite the broad deployment footprint of Chrome.
Uninitialized memory use in Skia, Chrome's 2D graphics engine, exposes a cross-origin data leak primitive in Google Chrome prior to 151.0.7922.109. Exploitation is constrained to attackers who have already achieved renderer process compromise - making this a second-stage, chained vulnerability rather than a standalone initial-access vector. No public exploit or active exploitation has been identified; SSVC rates this as non-automatable with partial technical impact, consistent with the low CVSS base score of 3.1.
Cross-origin data leakage in Google Chrome's Skia graphics library (versions prior to 151.0.7922.109) enables a remote attacker who has already achieved renderer process compromise to extract cross-origin data through a specially crafted HTML page. The vulnerability is classified CWE-457 (Use of Uninitialized Variable) and carries a low CVSS base score of 3.1, reflecting its dependency on a pre-existing renderer compromise as a prerequisite. No public exploit code has been identified at time of analysis, SSVC exploitation status is rated none, and a vendor-released patch is available in Chrome 151.0.7922.109.
Uninitialized GPU memory in Google Chrome on Android prior to 151.0.7922.109 exposes sensitive process memory contents to a remote attacker who has already achieved renderer process compromise. The CWE-457 flaw allows the GPU component to read and return uninitialized memory regions when processing attacker-controlled HTML, resulting in confidentiality impact bounded to the compromised process scope. No public exploit code exists and CISA SSVC rates exploitation as none at time of analysis, making this a second-stage information disclosure component rather than a standalone critical threat.
Firmware update integrity bypass in Insta InstaKNXServiceApp 1.2.3.1469 allows a remote network-positioned attacker to serve unauthenticated firmware or file lists to the application's update handler without detection. The vulnerable function CreateWebClientAndDownloadFileList fails to cryptographically verify the authenticity of data retrieved during the firmware update process (CWE-345), enabling substitution of malicious content. No patch has been released and the vendor did not respond to coordinated disclosure; no public exploit has been independently confirmed at time of analysis, though a GitHub gist linked in references may represent researcher-published proof-of-concept material.
Address bar spoofing in GNOME Epiphany 49.2 and earlier allows remote unauthenticated attackers to display a trusted domain in the browser UI while actually loading content from an attacker-controlled origin, enabling high-fidelity phishing attacks. Exploitation leverages RFC 3986 userinfo URL syntax - a crafted link such as `https://trusted.com:80@attacker.com/` causes Epiphany to render `trusted.com` in the address bar and security menus while WebKit fetches and renders `attacker.com`. No active exploitation has been confirmed (not in CISA KEV) and no public exploit code is identified at time of analysis, though the technique requires no tooling beyond a crafted URL.
Price manipulation via client-supplied ticket values in Event Booking Manager for WooCommerce (Pro) before 5.0.3 allows unauthenticated attackers to book paid event tickets at arbitrary prices, including free. The plugin's native (non-WooCommerce) checkout flow trusts the per-ticket price submitted by the client rather than re-deriving it from the server-side event configuration - a classic business logic failure. No public exploit or CISA KEV listing has been identified at time of analysis, but the attack requires no authentication and no special preconditions beyond the affected checkout mode being in use.
Payment bypass in RegistrationMagic WordPress plugin before 6.0.9.5 enables unauthenticated attackers to finalize arbitrarily-priced paid registrations using any previously-completed PayPal capture, regardless of its amount, currency, or intended payee. The plugin's server-side verification confirms only that a PayPal capture carries COMPLETED status, entirely omitting validation that the captured amount matches the registration fee, that the payee is the site's own account, or that the capture has not already been consumed. Because captures are not deduplicated, a single low-value legitimate capture can be replayed indefinitely to enroll unlimited users in high-value paid registrations at no cost - constituting scalable financial fraud. No public exploit or CISA KEV listing has been identified at time of analysis.
Payment notification forgery in WP Hotel Booking WordPress plugin before 2.3.2 allows unauthenticated remote users to obtain confirmed hotel bookings without submitting any real payment. The plugin fails to validate two critical conditions when processing inbound payment notifications: that the notification originates from the site's own merchant account, and that the reported payment amount matches the actual booking total. An attacker can exploit this by submitting a crafted payment callback (e.g., a fake IPN-style webhook) to have any booking marked as fully paid. No public exploit code has been identified at time of analysis, and this CVE is not listed in the CISA KEV catalog.
Price manipulation in WP Hotel Booking WordPress plugin before 2.3.3 allows unauthenticated remote attackers to create confirmed hotel reservations for free or at an arbitrarily reduced price by submitting negative room quantities or manipulated cart totals. The plugin trusts client-supplied cart data without server-side validation, enabling financial fraud against any hotel or accommodation operator running the unpatched plugin. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, though the attack requires no authentication and low complexity, making it trivially reproducible by any motivated attacker.
Unauthenticated payment notification forgery in the Five Star Restaurant Reservations WordPress plugin (all versions before 2.7.23) enables remote attackers to fraudulently mark arbitrary pending reservations as paid and confirmed without completing actual payment. The plugin's payment webhook handler accepts incoming IPN-style callbacks without verifying the notification's cryptographic authenticity, recipient identity, payment amount, transaction status, or binding to a specific booking - every control that prevents payment bypass is absent. No public exploit has been identified and this vulnerability is not listed in CISA KEV, but the CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates the attack is network-accessible, requires zero privileges and zero user interaction, making it accessible to unsophisticated actors.
Unauthorized membership activation in the Simple Membership WordPress plugin (before version 4.7.7) lets unauthenticated attackers obtain paid membership access at no cost by exploiting the absence of PayPal merchant account verification during payment notification processing. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms low-complexity, unauthenticated network exploitation requiring no user interaction. No public exploit or active exploitation has been identified at time of analysis; a vendor-released patch (version 4.7.7) is available.
Server-side validation bypass in the Easy Booking WordPress plugin (all versions before 3.5.0) allows unauthenticated remote attackers to circumvent minimum booking duration enforcement during cart addition and price calculation. Malicious users can submit manipulated add-to-cart requests with durations shorter than the merchant-configured minimums, completing orders at underpriced totals that the merchant is then expected to fulfill at a financial loss. No public exploit has been identified at time of analysis, though the unauthenticated, low-complexity attack vector makes this trivially reproducible by any remote attacker with HTTP access to the affected site.
Payment fraud via forged Worldpay webhooks affects the GetPaid WordPress plugin before version 2.8.55, allowing unauthenticated remote attackers to mark pending invoices as paid without making any actual payment. The plugin fails to verify the authenticity of incoming Worldpay Instant Payment Notifications (IPNs), meaning any attacker who can reach the webhook endpoint and reconstruct a plausible notification payload can manipulate invoice status. No public exploit has been identified at time of analysis, but the business logic impact - obtaining goods or services without payment - is direct and immediately harmful to affected merchants.
WP Travel Engine WordPress plugin before 6.8.2 allows unauthenticated attackers to fraudulently mark travel bookings as fully paid by exploiting missing PayPal IPN (Instant Payment Notification) validation. The plugin neither verifies that the incoming payment notification was directed to the site's configured merchant account nor confirms that the paid amount matches the booking total, enabling attackers to complete a minimal token payment to their own PayPal account and trigger a spoofed notification that the plugin blindly accepts. With a CVSS 5.3 and no public exploit or KEV listing at time of analysis, the technical severity appears moderate, but the business impact - obtaining travel services without payment - is materially higher than the base score reflects.
Request smuggling primitive in h2 (pip/h2) versions 4.4.0 and below enables network-accessible attackers to craft HTTP/2 header blocks containing duplicate Host headers that the library forwards verbatim to consuming applications. When a consumer downgrades the HTTP/2 request to HTTP/1.1 - a common pattern in reverse proxy and gateway architectures - the resulting HTTP/1.1 request carries two Host header lines, violating RFC 7230 and creating an ambiguity that downstream servers may interpret differently, enabling cache poisoning, security control bypass, or session hijacking. No active exploitation confirmed (not in CISA KEV); no public exploit code identified at time of analysis; fix is available in v4.4.1.
Out-of-bounds heap read in the node-re2 npm package (versions <= 1.26.0) exposes up to 3 bytes of adjacent heap memory per call to JavaScript when Buffer arguments ending in a truncated multi-byte UTF-8 lead byte are passed to replace() or split(). The overread is deterministic, requires no heap grooming, and a working proof-of-concept is included in the GitHub advisory. Applications that pass only strings - not Buffers - are entirely unaffected, but those that process untrusted Buffer input through re2 are at real risk of incremental heap disclosure. No CISA KEV listing was identified; this is a library-layer flaw fixed in re2@1.26.1.
Denial-of-service in Mermaid's radar-beta diagram renderer allows an attacker who can supply diagram input to trigger unbounded CPU and memory consumption by setting the `ticks` parameter to an arbitrarily large integer. Affected npm package versions >= 11.6.0 and < 11.16.1 perform no upper-bound validation on the `ticks` value, causing the JavaScript process - whether a browser tab or a server-side renderer - to freeze indefinitely until the OS terminates it due to OOM. A proof-of-concept is publicly available in the advisory. No KEV listing exists and no EPSS score is provided.
Prototype pollution in the Mermaid JavaScript diagramming library (npm/mermaid) exposes applications to JavaScript Object prototype manipulation when attacker-controlled data is incorrectly passed to configuration APIs. The `assignWithDepth` deep-merge helper used by `mermaid.initialize`, `mermaidAPI.setConfig`, and `mermaidAPI.updateSiteConfig` fails to sanitize `__proto__` keys, allowing an attacker to corrupt the shared Object prototype if a host application forwards user-supplied input into these configuration entry points - a usage pattern explicitly outside Mermaid's documented API contract. No public exploit has been identified and no CISA KEV listing exists; vendor risk assessment is low due to the non-standard application integration pattern required for exploitation.
Unsafe method invocation via Antlers template resolution in Statamic CMS enables unauthenticated remote attackers to destroy content and stored assets on affected installations. Sites running statamic/cms below 5.74.1 or in the 6.x line below 6.24.0 are vulnerable when their templates incorporate user-supplied input into Antlers template resolution - a deployment pattern present on developer-facing or dynamic sites. No public exploit or CISA KEV listing is identified at time of analysis; the CVSS AC:H rating reflects the required site-configuration precondition, tempering real-world exposure despite the destructive impact.
User enumeration via the Statamic CMS Control Panel exposes registered email addresses to any authenticated CP user, regardless of whether they hold the 'view users' permission. The `user.exists` POST endpoint - designed for the user creation wizard - returns a boolean confirming whether a given email is registered, allowing low-privileged CP accounts to enumerate the user directory without authorization. Affected versions are composer/statamic/cms below 5.74.1 (5.x branch) and 6.0.0-6.24.0 (6.x branch); no public exploit has been identified at time of analysis.
Cross-tenant namespace disclosure in LangGraph's PostgreSQL and SQLite checkpoint stores allows an authenticated low-privileged user to read stored items belonging to other namespaces without any crafted input. The flaw arises from translating hierarchical namespaces into dot-joined strings and scoping reads with SQL LIKE patterns that have no understanding of the segment separator, so a query scoped to 'foo' also returns data from 'foobar' or 'foo2'. Exploitation requires the specific precondition of prefix-overlapping or wildcard-containing namespace labels; no public exploit code exists and the vendor confirms no evidence of in-the-wild exploitation.
Timing side-channel exposure in Apache Portable Runtime Utility (APR-util) versions 1.2.0 through 1.6.3 allows network-accessible attackers to statistically recover passwords or hashes by measuring response-time variance in the `apr_password_validate()` function, which performs non-constant-time comparisons. The risk is materially elevated on platforms lacking native `crypt()` support - specifically Windows, Android, BeOS, and NetWare - where the non-constant-time code path is always exercised rather than conditionally. No public exploit has been identified at time of analysis, though the SSVC framework assesses the attack as automatable with partial technical impact.
Sensitive data exposure in the Gutenberg Blocks by Kadence Blocks WordPress plugin (versions <= 3.7.8) allows authenticated Contributor-level users to access information they should not be permitted to view. The CVSS vector (PR:L/C:L) confirms this is a low-privilege, partial confidentiality breach rather than a full data dump, limiting its severity to medium-low. No public exploit code has been identified and CISA KEV does not list this vulnerability, indicating no confirmed active exploitation at time of analysis.
Unauthenticated sensitive data exposure in the Featured Video Plus WordPress plugin (versions <= 2.3.3) allows any remote attacker to retrieve sensitive information without credentials via a crafted network request. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms this is exploitable against any default installation of the plugin with no prerequisites beyond network access. Classified under CWE-201, the plugin inserts sensitive information into its sent data, making it passively harvestable. No public exploit code or CISA KEV listing has been identified at time of analysis.
Unauthenticated sensitive data exposure in the Export Import Menus WordPress plugin (versions up to and including 1.9.2) allows remote, unauthenticated attackers to access sensitive information by invoking the plugin's export functionality without any credentials. Classified under CWE-201 (Insertion of Sensitive Information Into Sent Data), the plugin returns sensitive data in its HTTP responses to unauthenticated requests. No public exploit code has been identified at time of analysis, and this CVE does not appear on the CISA Known Exploited Vulnerabilities catalog.
Unauthenticated sensitive data exposure in the Custom CSS and JavaScript WordPress plugin (by WP Zone) versions up to and including 2.0.16 allows remote unauthenticated attackers to read sensitive information via network-accessible endpoints. Classified under CWE-201 (Insertion of Sensitive Information Into Sent Data), the flaw permits retrieval of data that the plugin transmits without requiring any authentication, with a CVSS 3.1 score of 5.3 (Medium). No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
Broken authentication in WP Event Solution WordPress plugin (versions ≤4.1.9) permits unauthenticated remote attackers to bypass authentication controls via an alternate path or channel (CWE-288), resulting in limited information disclosure and partial integrity impact. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms this is exploitable over the network with no credentials and no user interaction required against any WordPress installation running the affected plugin. No public exploit code and no CISA KEV listing have been identified at time of analysis.
Broken Authentication in Gutena Forms WordPress plugin (versions <= 1.9.0) allows unauthenticated remote attackers to bypass authentication controls, resulting in limited integrity and availability impacts against form configurations or submissions. The vulnerability is classified as CWE-288 (Authentication Bypass Using an Alternate Path or Channel) and was reported by Patchstack. No public exploit code or CISA KEV listing has been identified at time of analysis, but the low attack complexity and lack of authentication requirements make it straightforward to attempt against any exposed WordPress installation running the affected plugin.
Unauthenticated sensitive data exposure in the YITH WooCommerce Zoom Magnifier WordPress plugin (versions ≤ 2.52.0) permits remote, unauthenticated attackers to retrieve sensitive information without any credentials. Classified under CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere), the plugin exposes data through a network-accessible endpoint that lacks proper authorization controls. No public exploit code and no CISA KEV listing have been identified at time of analysis, though the low attack complexity makes opportunistic discovery straightforward.
RealHomes Memberships WordPress plugin before 3.1.0 permits any authenticated user - including low-privilege Subscribers - to claim paid membership packages for free by exploiting missing payment verification, absent nonce validation, and no capability checks on the membership grant endpoint. The business impact is direct financial loss for site operators running paid real estate membership tiers. No active exploitation has been confirmed by CISA KEV, but a public exploit is available via WPScan, lowering the barrier for abuse.
Business logic enforcement failure in WonderTrader's backtesting engine (versions up to 0.9.9) allows a low-privileged authenticated remote attacker to manipulate the internal limit order book cache through the MatchEngine::update_lob function in src/WtBtCore/MatchEngine.cpp. The flaw enables integrity-affecting manipulation of simulated or processed order book state in violation of expected matching workflow constraints. No vendor patch exists - the vendor did not respond to responsible disclosure - and proof-of-concept exploit code is publicly available (CVSS 4.0 E:P), though real-world risk is substantially bounded by the authentication requirement, low-only integrity impact, and niche deployment footprint.
Local privilege abuse in pardus-domain-joiner (TÜBİTAK BİLGEM Software Technologies Research Institute) before version 0.5.5 exposes Pardus Linux systems to unauthorized resource access through unverified ownership checks (CWE-283). A locally authenticated user with low privileges can trigger a code path where ownership of a resource is not validated before access or privileged operations are permitted, enabling privilege abuse. No public exploit code or active exploitation has been identified; the CVSS score of 3.3 reflects limited real-world impact confined to local sessions on Pardus Linux systems.
Improper input validation in OMICRON StationGuard 4.00 allows an adjacent network attacker to crash the IEC 61850 Sampled Values processing component by sending a specially crafted SV frame. The disruption is self-healing - the process restarts automatically and the failure is immediately surfaced to operators - leaving overall system availability and all other monitored traffic types unaffected. No public exploit code exists and this vulnerability is not listed in CISA KEV; the CVSS 4.0 score of 1.3 reflects the accurately bounded, minimal real-world impact.
openvpnserv on Windows insufficiently validates command line arguments received from its control socket before passing them to the openvpn.exe process, allowing a low-privileged local user to circumvent administrator-defined restrictions on permitted OpenVPN configuration directories. Affected installations span OpenVPN 2.4.0 through 2.6.21 and 2.7_alpha1 through 2.7.5 on Windows; fixed releases 2.6.22 and 2.7.6 shipped August 5, 2026. No public exploit or CISA KEV listing has been identified at time of analysis, though the CVSS 4.0 SC:H metric indicates that bypassing config directory controls could allow rogue VPN configurations to be loaded, with high downstream confidentiality impact on subsequent network systems.
Certificate validation bypass in OpenVPN 2.7 alpha series (mbedTLS builds) causes the --x509-username-field directive to unintentionally accept certificates that should be rejected, potentially granting unauthorized VPN network access. Only deployments running a 2.7 alpha or pre-release build compiled against mbedTLS and explicitly configured with --x509-username-field are exposed; OpenVPN 2.6.x stable series and OpenSSL-backend builds are not affected. The vendor characterizes this as a low-priority security finding; no public exploit has been identified at time of analysis and it is not listed in the CISA Known Exploited Vulnerabilities catalog.
eta-otp-lock before version 1.0.4 exposes sensitive information - likely OTP codes or credentials - as visible process arguments during invocation, enabling local system footprinting by other users. The vulnerability maps to CWE-214, where secrets passed via command-line arguments or process environment can be read by any local user through standard OS interfaces such as /proc or ps. No public exploit code exists and the product is not listed in CISA KEV, but the high confidentiality impact reflects the sensitivity of OTP material if intercepted.
Tenant isolation failure in WSO2 Identity Server allows authenticated low-privilege users to disclose personally identifiable information belonging to users in separate tenants. The vulnerability exists specifically when Email OTP, SMS OTP, or Magic Link are configured as first-factor authenticators - authentication requests processed through these flows lack sufficient validation to enforce organizational tenant boundaries, exposing data such as mobile numbers. No public exploit code or CISA KEV listing exists at time of analysis, but the low-complexity, network-accessible attack vector (CVSS PR:L/AV:N/AC:L) makes this a credible insider threat and compromised-account scenario for multi-tenant deployments.
Insufficient refresh token invalidation in WSO2 Identity Server's user impersonation flow allows a privileged attacker who has already obtained an impersonated access token to silently renew that authorization via the OAuth refresh token grant, sustaining unauthorized access well beyond the intended session lifetime. The integrity impact is two-fold: the attacker continues performing actions on behalf of the legitimate user, and audit logs attribute those actions to the victim identity rather than the true actor, corrupting traceability and compliance posture. No public exploit is identified and exploitation is bounded by high privilege prerequisites (PR:H) and adjacent network access (AV:A), placing realistic risk firmly in insider-threat and compromised-administrator scenarios.
Cross-organizational secret deletion in WSO2 Identity Server's Secret Type Management REST API allows an administrator with delete permissions to inadvertently remove secrets across all organizations in a multi-tenant deployment. The on-delete cascade logic, triggered when a secret type is deleted, fails to enforce organizational boundaries - a multi-tenancy isolation failure classified as CWE-281 (Improper Preservation of Permissions). Exploitation yields availability and integrity impact across the entire deployment, though it is constrained to high-privilege administrator accounts. No public exploit is identified and this vulnerability is not listed in the CISA KEV catalog.
Username enumeration via observable login response discrepancy affects WSO2 Identity Server, WSO2 Identity Server as Key Manager, WSO2 API Manager, WSO2 Open Banking AM, and WSO2 Open Banking IAM when the Multi-Attribute Login feature is enabled. When a valid username is submitted, the server resolves and returns the canonical form of that username; when an invalid username is submitted, the server echoes the raw input unchanged - creating a deterministic, scriptable oracle for account existence. This disclosure path persists regardless of the validate_username configuration setting, meaning a common hardening measure provides no defense. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
Incomplete session cleanup in poco-ai/poco-agent up to version 0.5.4 can permanently destroy the host user's ~/.claude directory - including all Claude Code chat history stored under ~/.claude/projects - when the agent runs outside a container environment. The WorkspaceManager._setup_session_persistence method performs an unconditional rmtree followed by a symlink swap on ~/.claude without verifying a container context, and the corresponding cleanup phase can additionally unlink pre-existing ~/.claude symlinks unrelated to poco-agent. A publicly available exploit exists via GitHub issue #131 and PR #132, though the CVSS 4.0 base score of 2.9 reflects high attack complexity and impact limited to low integrity and availability loss with no confidentiality breach.
File inclusion in TinyAGI 0.0.20 exposes server-side files to remote unauthenticated attackers through the buildSystemPrompt function in packages/server/src/routes/agents.ts. Exploitation requires no privileges or user interaction, and a publicly available proof-of-concept exists via GitHub issue #283. No patch has been released - the vendor has not responded to the responsible disclosure despite being notified through the project's issue tracker.
In the Linux kernel, the following vulnerability has been resolved: iio: adc: spear: Initialize completion before requesting IRQ In the report from Jaeyoung Chung: "spear_adc_probe() in drivers/iio/adc/spear_adc.c registers its interrupt handler with devm_request_irq() before it initializes st->completion with init_completion(). If an interrupt arrives after devm_request_irq() and before init_completion(), the handler calls complete() on an uninitialized completion, causing a kernel panic. The probe path, in spear_adc_probe(): iodev = devm_iio_device_alloc(&pdev->dev, sizeof(*st)); /* st kzalloc-zeroed */ ... retval = devm_request_irq(&pdev->dev, irq, spear_adc_isr, 0, LPC32XXAD_NAME, st); /* register handler */ ... init_completion(&st->completion); /* initialize completion */ spear_adc_isr() calls complete(): complete(&st->completion); If the device raises an interrupt before init_completion() runs, complete() acquires the uninitialized wait.lock and walks the zeroed task_list in swake_up_locked(). The zeroed task_list makes list_empty() return false, so swake_up_locked() dereferences a NULL list entry, triggering a KASAN wild-memory-access." Fix the chance of a spurious IRQ causing an uninitialized pointer dereference by moving init_completion() above devm_request_irq().
In the Linux kernel, the following vulnerability has been resolved: HID: hid-lenovo-go: cancel cfg_setup work in hid_go_cfg_remove() hid_go_cfg_probe() initialises drvdata.go_cfg_setup and schedules it to run 2 ms later: INIT_DELAYED_WORK(&drvdata.go_cfg_setup, &cfg_setup); schedule_delayed_work(&drvdata.go_cfg_setup, msecs_to_jiffies(2)); cfg_setup() dereferences drvdata.hdev to issue MCU command requests. hid_go_cfg_remove() tears down sysfs and stops the HID device, but never drains the delayed work. If the device is unbound within the 2 ms scheduling delay (a probe failure rolling back via remove, or a fast rmmod after probe), the work fires after hid_destroy_device() has dropped its reference and released the underlying hdev struct, leaving cfg_setup() with a stale drvdata.hdev pointer. Mirror the sibling driver hid-lenovo-go-s.c, whose hid_gos_cfg_remove() already calls cancel_delayed_work_sync() on its analogous work, and drain go_cfg_setup at the top of hid_go_cfg_remove(). The cancel must come before guard(mutex)(&drvdata.cfg_mutex) because cfg_setup() acquires that mutex; reversing the order would deadlock.
In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_fs: initialize reset_work at allocation time ffs_fs_kill_sb() unconditionally calls cancel_work_sync() on ffs->reset_work when a functionfs instance is unmounted: ffs_data_reset(ffs); cancel_work_sync(&ffs->reset_work); However ffs->reset_work is only ever initialized via INIT_WORK() in ffs_func_set_alt() and ffs_func_disable(), and only on the FFS_DEACTIVATED path. That state is reached solely by ffs_data_closed() when the instance is mounted with the "no_disconnect" option, so for the common case (no "no_disconnect", or mounted and unmounted without ever being deactivated) reset_work is never initialized. ffs_data_new() allocates the ffs_data with kzalloc_obj() and does not initialize reset_work, and ffs_data_reset()/ffs_data_clear() do not touch it either, so reset_work.func is left NULL. cancel_work_sync() on such a work then trips the WARN_ON(!work->func) guard in __flush_work(): WARNING: kernel/workqueue.c:4301 at __flush_work+0x330/0x360, CPU#3: umount Call trace: __flush_work cancel_work_sync ffs_fs_kill_sb [usb_f_fs] deactivate_locked_super deactivate_super cleanup_mnt __cleanup_mnt task_work_run exit_to_user_mode_loop el0_svc On older kernels cancel_work_sync() on a zero-initialized work struct was a silent no-op, which hid the missing initialization. Initialize reset_work once in ffs_data_new() so it is always valid for the lifetime of the ffs_data, and drop the now-redundant INIT_WORK() calls from the two deactivation paths.
In the Linux kernel, the following vulnerability has been resolved: dma-buf/udmabuf: skip redundant cpu sync to fix cacheline EEXIST warning When CONFIG_DMA_API_DEBUG_SG is enabled, importing a udmabuf into a DRM driver (e.g. amdgpu for video playback in GNOME Videos / Showtime) triggers a spurious warning: DMA-API: amdgpu 0000:03:00.0: cacheline tracking EEXIST, \ overlapping mappings aren't supported WARNING: kernel/dma/debug.c:619 at add_dma_entry+0x473/0x5f0 The call chain is: amdgpu_cs_ioctl -> amdgpu_ttm_backend_bind -> dma_buf_map_attachment -> [udmabuf] map_udmabuf -> get_sg_table -> dma_map_sgtable(dev, sg, direction, 0) // attrs=0 -> debug_dma_map_sg -> add_dma_entry -> EEXIST This happens because udmabuf builds a per-page scatter-gather list via sg_set_folio(). When begin_cpu_udmabuf() has already created an sg table mapped for the misc device, and an importer such as amdgpu maps the same pages for its own device via map_udmabuf(), the DMA debug infrastructure sees two active mappings whose physical addresses share cacheline boundaries and warns about the overlap. The DMA_ATTR_SKIP_CPU_SYNC flag suppresses this check in add_dma_entry() because it signals that no CPU cache maintenance is performed at map/unmap time, making the cacheline overlap harmless. All other major dma-buf exporters already pass this flag: - drm_gem_map_dma_buf() passes DMA_ATTR_SKIP_CPU_SYNC - amdgpu_dma_buf_map() passes DMA_ATTR_SKIP_CPU_SYNC The CPU sync at map/unmap time is also redundant for udmabuf: begin_cpu_udmabuf() and end_cpu_udmabuf() already perform explicit cache synchronization via dma_sync_sgtable_for_cpu/device() when CPU access is requested through the dma-buf interface. Pass DMA_ATTR_SKIP_CPU_SYNC to dma_map_sgtable() and dma_unmap_sgtable() in udmabuf to suppress the spurious warning and skip the redundant sync.
In the Linux kernel, the following vulnerability has been resolved: i2c: core: fix NULL-deref on adapter registration failure If adapter registration ever fails the release callback would trigger a NULL-pointer dereference as the completion struct has not been initialised. Note that before the offending commit this would instead have resulted in a minor memory leak of the adapter name.
File inclusion via unsanitized path input in TinyAGI 0.0.20's Message API Endpoint exposes server-side files to remote unauthenticated attackers. The vulnerable surface is the `collectFiles` function in `packages/core/src/response.ts`, which accepts externally controlled file paths without adequate validation (CWE-73). Publicly available exploit code exists via GitHub issue #282, and the project maintainer had not issued a patch or response at time of disclosure - compounding risk for any internet-exposed deployments.
Symlink escape in openclaw-cn's apply_patch Tool allows authenticated remote attackers on versions up to 0.2.1 to traverse outside the intended sandbox boundary by exploiting a failure in the assertNoSymlinkEscape validation function in src/agents/sandbox-paths.ts. Attackers with low-level access can craft symbolic links within the sandbox that resolve to paths outside it, yielding limited unauthorized read and write access to the underlying filesystem. A public proof-of-concept exploit is documented in GitHub issue #566, and no vendor patch has been released as the project has not responded to disclosure.
Cleartext exposure of third-party API keys and authentication tokens in AI Engine WordPress plugin (before 3.6.4) allows Editor-role users to read secrets that are intended to be administrator-only. The plugin inlines sensitive configuration values into admin page JavaScript without redaction, making them readable to any authenticated user with Editor access who inspects the page source. A public proof-of-concept exists per WPScan, though EPSS remains low at 0.17% (7th percentile) and the vulnerability is not in the CISA KEV catalog.
tourmaster WordPress plugin (all versions before 5.4.9) exposes exported customer booking and order data via a fixed, predictable file path inside its publicly accessible web directory, with no authentication or access control enforcing download restrictions. Any unauthenticated network attacker who knows or can derive the static export file URL can retrieve personally identifiable information - names, contact details, and booking records - after an administrator has triggered an export. A publicly available proof-of-concept exists per WPScan, and exploitation is fully automatable (SSVC), though EPSS sits at 0.14% and no CISA KEV listing exists at time of analysis.
Unauthorized retrieval of other customers' payment receipt images is possible in PeproDev WooCommerce Receipt Uploader (≤ 2.8.0) because the plugin's token-based attachment access mechanism never validates that a requested attachment ID belongs to the order the token was issued for. Unauthenticated network attackers can forge or repurpose a token - trivially obtained by placing any order - to iterate over attachment IDs and exfiltrate payment receipts uploaded by unrelated customers, potentially exposing financial documents containing banking details or PII. A publicly available proof-of-concept exists per WPScan reporting (EUVD-2026-53719); no CISA KEV listing indicates widespread active exploitation has not been confirmed, though SSVC rates the attack as automatable.
Incorrect privilege assignment in cosmicstack-labs mercury-agent (all versions through 1.1.12) allows authenticated remote attackers to bypass shell command permission checks via the run_command Handler. The flaw resides in the PermissionManager.checkShellCommand function within src/capabilities/permissions.ts, where privilege levels are not correctly validated, potentially enabling a low-privileged user to execute shell commands exceeding their authorized scope. A public proof-of-concept exploit exists via GitHub issue #72, and the project maintainer has not responded to responsible disclosure, leaving no vendor-released patch available at time of analysis.
Information disclosure in netease-youdao LobsterAI 2026.6.10 exposes sensitive data through manipulation of the MEDIA Path Handler component. The vulnerable function parseMediaTokensFromText in src/renderer/services/artifactParser.ts can be triggered remotely when a user interacts with attacker-controlled content, leaking confidential information such as local file system paths or internal metadata. A publicly available exploit exists via GitHub issue #2176, and the vendor has not responded to coordinated disclosure, leaving no patch available at time of analysis.
Incorrect privilege assignment in NousResearch hermes-agent through 0.16.0 allows authenticated remote users to invoke toolsets that administrators have explicitly disabled via the disabled_toolsets configuration. The flaw resides in get_tool_definitions within agent/agent_init.py, where the disabled_toolsets list was not checked before injecting tool definitions into an agent session, causing disabled tools (e.g., 'memory') to remain fully accessible. No active exploitation is confirmed (not in CISA KEV), but a public proof-of-concept exists via GitHub issue #46171 and an upstream fix is available in PR #46185.
Unauthenticated remote information disclosure in heshengtao super-agent-party (up to version 0.4.1) allows remote attackers to read sensitive file content by manipulating the tool_name or tool_params arguments passed to the get_file_content function via the execute_tool_manually endpoint in server.py. The flaw requires no authentication and no user interaction, and a public proof-of-concept exploit is available on GitHub. No patch has been issued; the vendor did not respond to coordinated disclosure.
Out-of-bounds heap read in HDF5's N-Bit filter decompression affects all versions through 2.3.0, allowing an attacker who can deliver a crafted HDF5 file to a user or automated pipeline to trigger application crashes and, in constrained cases, leak adjacent heap memory contents into decompressed dataset values. The three affected functions - H5Z__nbit_decompress_one_byte, H5Z__nbit_decompress_one_nooptype, and H5Z__nbit_decompress_one_atomic - advance a buffer read index without bounding it against the actual compressed chunk size, exploitable whenever H5Dread is invoked, including via common tools like h5ls and h5repack. No public exploit code has been identified at time of analysis, and this vulnerability is not listed in the CISA KEV catalog.
Unauthorized component instantiation in Nuxt server islands (versions >=3.1.0 <3.21.10 and >=4.0.0 <4.5.1) allows remote unauthenticated attackers to render arbitrary globally-registered Vue components or native HTML elements - including constructs like `<iframe>` - by supplying a crafted string prop to the `/__nuxt_island/` endpoint. The attack exploits Vue's attribute fallthrough behavior: props an island does not declare pass through to its root element, so if that root is a polymorphic component (such as reka-ui or @nuxt/ui elements using an `as` prop), the attacker's string silently reaches dynamic component resolution without any explicit forwarding in the island author's code. Unlike the related RCE vector GHSA-9473-5f9j-94wq, this does not require `vue.runtimeCompiler`, making it reachable in substantially more configurations; however, no public exploit has been identified at time of analysis and real-world exploitation is constrained by application-specific island configuration requirements.
Credential exposure in HCL Digital Experience and Digital Experience Compose allows sensitive authentication material to be written to web server logs under specific, non-default configurations when the default login portlet is in use. The flaw, classed as CWE-522 (Insufficiently Protected Credentials), means that any party with read access to web server logs - such as operations staff, log aggregation systems, or an attacker who has compromised a log pipeline - may recover cleartext or weakly protected user credentials. No public exploit code has been identified at time of analysis, and active exploitation has not been confirmed by CISA KEV.
Authenticated users in IBM Langflow OSS 1.0.0 through 1.10.3 can exploit a privileged built-in component to read arbitrary server-side environment variables, bypassing security controls designed to restrict custom component execution. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H) confirms this is a low-complexity, network-accessible flaw requiring only standard user credentials, with high confidentiality impact. No active exploitation confirmed via CISA KEV, and no public exploit code has been identified at time of analysis; IBM has released a patch via its support portal.
Prototype pollution via Electron's contextBridge allows untrusted renderer-side web content to smuggle a malicious prototype across the isolation boundary into preload script context, bypassing context isolation in versions prior to 39.8.9, 40.9.2, 41.2.2, and 42.0.0-beta.4. Exploitation is conditional on preload scripts accepting object arguments from untrusted content and reading inherited properties without own-property guards. No public exploit has been identified at time of analysis, and the flaw is not listed in CISA KEV; however, the scope-change (S:C) CVSS metric reflects that a successful attack crosses the renderer-to-preload privilege boundary, which can have amplified consequences in apps that expose sensitive Node.js APIs through the bridge.
Credential exposure in Cisco RoomOS allows an authenticated low-privilege local user to capture user login credentials by enabling a specific debug logging level and collecting the resulting system logs. The flaw (CWE-532) spans a wide version range from RoomOS 10.x through 26.x across Cisco's entire room collaboration device portfolio. No public exploit code has been identified and this CVE does not appear in the CISA KEV catalog at time of analysis, but the High confidentiality impact - plaintext credential disclosure - warrants prioritized patching on any device with non-administrative local accounts.
Cleartext credential exposure in Cisco Catalyst SD-WAN Manager's web-based management interface allows an authenticated low-privileged remote attacker to read sensitive authentication material from system logs. The root cause is an incomplete encryption allowlist: specific template types are excluded from the encryption policy, resulting in sensitive values being written to logs in cleartext - accessible both on the local system and on any configured remote logging server. No public exploit code has been identified and this vulnerability is not listed in CISA KEV, but successful exploitation directly enables credential theft that can cascade into broader SD-WAN infrastructure compromise.
Privilege escalation via command injection in Cisco Integrated Management Controller (IMC) allows authenticated Admin-level attackers to execute arbitrary OS commands and elevate to root on affected Cisco UCS Standalone and E-Series systems. Exploitation requires Admin credentials to the web-based management interface but results in full OS root access, which Cisco rates as High SIR despite a CVSS 6.5 (Medium) score - explicitly noting that root attainment carries security implications beyond what the base score reflects. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis.
Electron's window.open() features string parsing forwards untrusted BrowserWindowConstructorOptions directly to child BrowserWindows without an allowlist, allowing renderer-side web content to supply privileged options - such as icon - that cause the trusted main process to access attacker-chosen file or network paths. All Electron apps serving untrusted web content without a setWindowOpenHandler guard are affected across the 39.x, 40.x, 41.x, and 42.x beta series. No public exploit code has been identified and this vulnerability is not listed in the CISA KEV catalog; the practical attack surface is narrowed to apps that load third-party or user-controlled content and omit the recommended setWindowOpenHandler override.
Bolt protocol handshake decoder in Neo4j Enterprise and Community Editions fails to distinguish overlong capability masks from truncated ones, leaving server-side channels permanently open without producing a finalization message. Any unauthenticated client reaching the Bolt connector (default TCP 7687) can trigger this pre-authentication stall by sending 32 continuation bytes in the capability mask, causing the decoder to loop on the same unread bytes. The CVSS 4.0 vector carries E:P (proof of concept exists) with a low availability impact; no active exploitation has been confirmed via CISA KEV, but the trivial pre-auth trigger and POC availability increase realistic risk to exposed Bolt endpoints.
Session isolation bypass in Electron's custom protocol handler allows cached HTTP responses from defaultSession to leak across otherwise isolated session partitions. Electron versions 40.x through pre-release 43.x are affected when apps use ProtocolResponse.url without specifying ProtocolResponse.session, causing upstream requests to be routed through defaultSession regardless of which session registered the protocol handler. An attacker who can trigger a cross-session cache hit may read confidential session-scoped content (C:H) or partially influence cached responses (I:L) intended for a different, isolated session; no public exploit or CISA KEV listing exists at time of analysis.
IBM Maximo Application Suite 9.0, 9.1, and 9.2 fails to set the `Secure` attribute on authorization tokens and session cookies, enabling interception of credential material over unencrypted HTTP. An attacker who tricks an authenticated user into following an HTTP link - via phishing or a malicious page - causes the victim's browser to transmit the session cookie in plaintext, where it can be captured by a server the attacker controls or via network sniffing. No public exploit has been identified at time of analysis and the vulnerability is not listed in the CISA KEV catalog; however, session token theft can lead to full account takeover, meaningfully exceeding the limited confidentiality scope implied by the raw CVSS score.
Session data tampering in IBM Maximo Application Suite 9.0, 9.1, and 9.2 is possible because the application signs session tokens with a weak HMAC secret, classified under CWE-330 (Use of Insufficiently Random Values). A remote unauthenticated attacker who can derive or predict the HMAC signing key may forge or modify session tokens, undermining session integrity across affected deployments. No public exploit code has been identified, this vulnerability is not listed in the CISA KEV catalog, and a vendor patch is available via IBM's advisory.
Improper TLS hostname verification in IBM Business Automation Workflow exposes high-privilege sessions to man-in-the-middle interception by failing to validate that server certificates match the target hostname. Affected deployments span both containerized (Kubernetes/OpenShift) and traditional on-premises models across multiple release trains from 24.0.0 through 26.0.0. No public exploit has been identified and the vulnerability is not listed in CISA KEV; real-world risk is substantially bounded by the PR:H requirement - an attacker must already hold administrative credentials before exploitation is feasible.
Unauthenticated remote information disclosure in IBM Cloud Pak for Business Automation 24.0.0 through 26.0.0 allows network attackers to retrieve sensitive data embedded in externally accessible manifest files. The vulnerability stems from CWE-538, where sensitive configuration or operational data is written into manifest files that are not adequately protected from external access. No public exploit has been identified at time of analysis, and a vendor patch is available via IBM's support portal.
Electron's permission check handler incorrectly exposes cross-origin iframes to unauthorized camera, microphone, and serial port access by passing the top-level frame's origin as `requestingOrigin` instead of the requesting iframe's own origin. Applications implementing `session.setPermissionCheckHandler` with origin-based grant logic that also embed cross-origin iframes with delegated device permissions are affected - the handler is deceived into approving the iframe's request as if it came from the trusted top-level origin. No public exploit code exists and CISA KEV listing is not confirmed; the CVSS score of 5.9 with AC:H accurately reflects the specific multi-condition deployment pattern required for exploitation.
Out-of-bounds memory read in Electron's offscreen rendering pipeline allows a compromised GPU process to cause the browser/main process to read beyond a shared memory mapping boundary when producing `paint` event images, disclosing process memory or crashing the application. Exploitation requires two independent preconditions: the host application must enable `webPreferences.offscreen` (non-default) and an attacker must have already achieved code execution in the GPU process via a separate vulnerability. No public exploit code has been identified at time of analysis, and this vulnerability is not listed in the CISA KEV catalog.
Arbitrary file write via crafted tar archive extraction in Jenkins 2.575 and earlier allows attackers controlling agent processes to escape extraction directory boundaries on the controller filesystem, directly enabling remote code execution. The root cause is unsafe handling of symbolic links with effectively empty names during .tar and .tar.gz extraction on the controller, permitting writes to sensitive paths such as JENKINS_HOME/init.groovy.d/ (Groovy init scripts) or JENKINS_HOME/plugins/ (plugin deployment). No public exploit or CISA KEV listing has been identified at time of analysis, but the agent-to-controller trust boundary is a well-established Jenkins attack surface with a history of critical exploitation.
Remote code execution and privilege escalation across Jenkins core and multiple plugins were disclosed in the 2026-08-05 security advisory, with the most critical issue being a JEP-200 deserialization filter bypass (CVE-2026-70426) in Remoting 3384.v60d89463d9e0 and earlier that allows agent processes or holders of Agent/Connect permission to execute arbitrary code on the Jenkins controller. Compounding this, two separate arbitrary file-write primitives (CVE-2026-70427 via malicious tar archives, CVE-2026-70428 via path traversal in file parameter names) independently enable code execution by writing into JENKINS_HOME/init.groovy.d/ or deploying rogue plugins. No public exploit code or CISA KEV listing was identified at time of analysis, but the attack surface spans both network-accessible agents and authenticated users with low-privilege build permissions.
SELinux label manipulation via TOCTOU race condition in the policycoreutils fixfiles script allows a local low-privileged attacker to corrupt SELinux mandatory access control labels on arbitrary system files, including security-critical targets such as /etc/shadow. The flaw affects fixfiles when run in relabel or restore mode across all supported Red Hat Enterprise Linux releases (6 through 10), Red Hat Hardened Images, and OpenShift Container Platform 4. No public exploit code or active exploitation has been identified at time of analysis, and exploitation is constrained by both a required race condition win and the need for an administrator to actively invoke fixfiles.
TLS credential exposure in ZTE ZXHN F680 fiber gateway firmware allows an adjacent-network attacker to extract unencrypted cryptographic key material - classified under CWE-321 (Use of Hard-coded Cryptographic Key) - enabling potential decryption or impersonation of TLS-protected communications between the device and upstream ISP services. Seven discrete firmware versions are confirmed affected per the ENISA EUVD entry and ZTE's own advisory. No public exploit code or CISA KEV listing is confirmed at time of analysis, and the CVSS adjacency requirement and high complexity rating limit realistic exploitation to technically capable actors with local network proximity.
Root password hash exposure in ZTE F689 firmware allows a physical attacker to extract credential material stored in cleartext or weakly protected form within the device firmware image. The F689 is an ISP-deployed broadband gateway, and this vulnerability (CWE-916) means the hash protecting root-level access uses insufficient computational effort, making offline cracking feasible once extracted. No public exploit code has been identified and no active exploitation is confirmed; however, successful hash recovery grants an attacker a path to persistent root-level device compromise.
Out-of-Bounds Read in Autodesk's image handling library crashes Revit and AutoCAD when a user opens a maliciously crafted TIF file during image import. Affected products span Revit 2024, 2026, and 2027 as well as AutoCAD and AutoCAD LT 2027, all below vendor-specified fix versions. The attack is local and requires user interaction, limiting automated mass exploitation, but remains a viable denial-of-service vector in targeted scenarios against AEC professionals who routinely handle externally sourced CAD assets. No public exploit identified at time of analysis.
Reverse tabnabbing in PILOS versions 2.1.0 through 4.14.1 exposes authenticated users to session hijacking via phishing by omitting the Cross-Origin-Opener-Policy (COOP) response header on pages that open links in new browser tabs. When an authenticated user clicks a target="_blank" link within PILOS, the newly opened page retains a live window.opener reference to the original PILOS tab, allowing the destination page to silently redirect that tab to an attacker-controlled site mimicking PILOS login. No public exploit has been identified at time of analysis, and the vendor-confirmed fix is available in v4.14.1.
Uninitialized heap memory disclosure in FFmpeg's native TIFF decoder (libavcodec/tiff.c) exposes stale heap contents to any party able to retrieve decoded image output. Affected versions span 0.5 through 8.x; FFmpeg 9.0 carries the upstream fix. In server-side media pipelines that accept and return processed TIFF files - transcoding APIs, thumbnail generators, upload handlers - an attacker can craft a structurally valid Deflate-compressed TIFF strip that inflates short, causing the decoder to embed prior heap allocation remnants into the decoded output, potentially leaking sensitive in-process data. No active exploitation is confirmed (not in CISA KEV) and no standalone public exploit code was identified at time of analysis.
Uninitialized heap memory read in FFmpeg's native Screenpresso decoder (libavcodec/screenpresso.c) allows an attacker who can supply crafted SPV1-encoded video to recover stale heap contents - including userspace addresses and prior-frame data - from the process decoding the media. Affected versions span FFmpeg 3.0 through 8.x; version 9.0 resolves the issue via upstream commits and PR #23896. No active exploitation is confirmed in CISA KEV, and no public exploit code has been identified at time of analysis, but the information-disclosure primitive is particularly dangerous in persistent server-side decoding pipelines where heap residue from earlier operations may include sensitive material.
Heap memory disclosure in FFmpeg's native RSCC decoder (libavcodec/rscc.c) allows an attacker who can supply a crafted video file to expose residual heap contents - including data from prior heap allocations or previously decoded frames - to any downstream consumer of the decoded output. The flaw stems from rscc_decode_frame() calling av_image_copy_plane() without verifying that the number of decompressed bytes matches the declared tile geometry, allowing the unwritten suffix of the persistent ctx->inflated_buf to propagate silently into the output frame. All FFmpeg builds from 3.0 through 8.x are affected; no public exploit has been identified at time of analysis, and no KEV listing exists.
In the Linux kernel, the following vulnerability has been resolved: x86/bugs: Make Safe-RET robust against interrupt injection An attacker injecting interrupts while the Safe-RET mitigation executes on machines affected by SRSO can neutralize the safe return sequence, potentially leading to data leakage through speculative execution. Fixup register state as if the Safe-RET sequence executed successfully by "emulating" it, in a manner of speaking, and avoid executing a RET instruction after returning from the interrupt.
Terminal escape sequence injection in GitHub CLI (gh) prior to version 2.97.0 allows an attacker who controls content on GitHub - gists, pull requests, releases, codespaces, API responses, skills, or agent-task output - to embed ANSI/VT escape sequences that are rendered verbatim by the victim's terminal when they run any of the affected display commands. Impact ranges from cosmetic screen manipulation (title bar spoofing, on-screen content overwrite) to, on certain terminal emulators that interpret shell-integration or hyperlink escape sequences, arbitrary command execution in the user's shell. This issue broadens the same CWE-150 class addressed by CVE-2026-45803, which patched only the `gh run view --log` path, to the full set of content-displaying subcommands. No public exploit or KEV listing is present at time of analysis, though the injection surface is wide and the fix is confirmed in v2.97.0.
GitHub CLI's `gh auth status` command in versions prior to 2.97.0 partially exposed fine-grained personal access tokens and GitHub App tokens in terminal and CI output due to a flawed masking algorithm. The defect used `strings.LastIndexByte` to find the last underscore as the masking boundary - for tokens like `github_pat_APPID_secretbody` or `ghs_APPID_JWT`, this left the middle segment (between the type prefix and the last underscore) visible in plain text. Affected token types include fine-grained PATs (`github_pat_*`), GitHub App installation tokens (`ghs_*`), user access tokens (`ghu_*`), and the Actions `GITHUB_TOKEN`; classic tokens (`gho_*`, `ghp_*`) are not affected. No public exploit is identified at time of analysis.
Session cookie theft in the DataPress (Dataverse Integration) WordPress plugin before 2.91 allows any Contributor-level user to steal session credentials from higher-privileged users such as Editors or Administrators. The plugin's template rendering feature improperly exposes the session data of users who view affected content, enabling privilege escalation via session hijacking. No public exploit code has been identified at time of analysis, but the low barrier to entry (Contributor role) makes this a realistic insider or compromised-low-privilege-account threat against WordPress sites using this plugin.
Unauthenticated information disclosure in OpenReception appointment-booking-software prior to version 1.0.5 exposes private channel metadata through the public `/api/tenants/{id}/schedule` endpoint, bypassing the `isPublic` flag that governs channel visibility in the booking UI. Any caller with a valid tenant ID can retrieve channel names, descriptions, IDs, agent associations, pause status, confirmation requirements, and computed slot availability for channels deliberately configured as internal-only - data that the product's own design intends to hide from public callers. No public exploit has been identified and the vulnerability is not listed in CISA KEV, but the CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms trivial unauthenticated reachability requiring no special conditions.
Out-of-bounds heap read in llama.cpp's recurrent memory state restore path (builds b5702 through b7653) allows an attacker with write access to the slot save directory to craft a malicious slot file that triggers heap data leakage - including pointer values - into server logs, effectively defeating ASLR protections and enabling multi-stage exploitation. No public exploit has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalogue. An upstream fix is available as a commit to the ggml-org/llama.cpp repository, though a tagged released version past the affected build range has not been independently confirmed.
Cross-origin data leakage in Google Chrome's GPU process - caused by an integer overflow (CWE-190) - enables a remote attacker who has already achieved renderer process compromise to read data across origin boundaries by delivering a crafted HTML page. All Chrome desktop releases prior to 151.0.7922.109 are affected. No public exploit or CISA KEV listing exists at time of analysis; the chained nature of the attack (requiring a prior renderer compromise) substantially constrains real-world risk despite the broad deployment footprint of Chrome.
Uninitialized memory use in Skia, Chrome's 2D graphics engine, exposes a cross-origin data leak primitive in Google Chrome prior to 151.0.7922.109. Exploitation is constrained to attackers who have already achieved renderer process compromise - making this a second-stage, chained vulnerability rather than a standalone initial-access vector. No public exploit or active exploitation has been identified; SSVC rates this as non-automatable with partial technical impact, consistent with the low CVSS base score of 3.1.
Cross-origin data leakage in Google Chrome's Skia graphics library (versions prior to 151.0.7922.109) enables a remote attacker who has already achieved renderer process compromise to extract cross-origin data through a specially crafted HTML page. The vulnerability is classified CWE-457 (Use of Uninitialized Variable) and carries a low CVSS base score of 3.1, reflecting its dependency on a pre-existing renderer compromise as a prerequisite. No public exploit code has been identified at time of analysis, SSVC exploitation status is rated none, and a vendor-released patch is available in Chrome 151.0.7922.109.
Uninitialized GPU memory in Google Chrome on Android prior to 151.0.7922.109 exposes sensitive process memory contents to a remote attacker who has already achieved renderer process compromise. The CWE-457 flaw allows the GPU component to read and return uninitialized memory regions when processing attacker-controlled HTML, resulting in confidentiality impact bounded to the compromised process scope. No public exploit code exists and CISA SSVC rates exploitation as none at time of analysis, making this a second-stage information disclosure component rather than a standalone critical threat.
Firmware update integrity bypass in Insta InstaKNXServiceApp 1.2.3.1469 allows a remote network-positioned attacker to serve unauthenticated firmware or file lists to the application's update handler without detection. The vulnerable function CreateWebClientAndDownloadFileList fails to cryptographically verify the authenticity of data retrieved during the firmware update process (CWE-345), enabling substitution of malicious content. No patch has been released and the vendor did not respond to coordinated disclosure; no public exploit has been independently confirmed at time of analysis, though a GitHub gist linked in references may represent researcher-published proof-of-concept material.
Address bar spoofing in GNOME Epiphany 49.2 and earlier allows remote unauthenticated attackers to display a trusted domain in the browser UI while actually loading content from an attacker-controlled origin, enabling high-fidelity phishing attacks. Exploitation leverages RFC 3986 userinfo URL syntax - a crafted link such as `https://trusted.com:80@attacker.com/` causes Epiphany to render `trusted.com` in the address bar and security menus while WebKit fetches and renders `attacker.com`. No active exploitation has been confirmed (not in CISA KEV) and no public exploit code is identified at time of analysis, though the technique requires no tooling beyond a crafted URL.
Price manipulation via client-supplied ticket values in Event Booking Manager for WooCommerce (Pro) before 5.0.3 allows unauthenticated attackers to book paid event tickets at arbitrary prices, including free. The plugin's native (non-WooCommerce) checkout flow trusts the per-ticket price submitted by the client rather than re-deriving it from the server-side event configuration - a classic business logic failure. No public exploit or CISA KEV listing has been identified at time of analysis, but the attack requires no authentication and no special preconditions beyond the affected checkout mode being in use.
Payment bypass in RegistrationMagic WordPress plugin before 6.0.9.5 enables unauthenticated attackers to finalize arbitrarily-priced paid registrations using any previously-completed PayPal capture, regardless of its amount, currency, or intended payee. The plugin's server-side verification confirms only that a PayPal capture carries COMPLETED status, entirely omitting validation that the captured amount matches the registration fee, that the payee is the site's own account, or that the capture has not already been consumed. Because captures are not deduplicated, a single low-value legitimate capture can be replayed indefinitely to enroll unlimited users in high-value paid registrations at no cost - constituting scalable financial fraud. No public exploit or CISA KEV listing has been identified at time of analysis.
Payment notification forgery in WP Hotel Booking WordPress plugin before 2.3.2 allows unauthenticated remote users to obtain confirmed hotel bookings without submitting any real payment. The plugin fails to validate two critical conditions when processing inbound payment notifications: that the notification originates from the site's own merchant account, and that the reported payment amount matches the actual booking total. An attacker can exploit this by submitting a crafted payment callback (e.g., a fake IPN-style webhook) to have any booking marked as fully paid. No public exploit code has been identified at time of analysis, and this CVE is not listed in the CISA KEV catalog.
Price manipulation in WP Hotel Booking WordPress plugin before 2.3.3 allows unauthenticated remote attackers to create confirmed hotel reservations for free or at an arbitrarily reduced price by submitting negative room quantities or manipulated cart totals. The plugin trusts client-supplied cart data without server-side validation, enabling financial fraud against any hotel or accommodation operator running the unpatched plugin. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, though the attack requires no authentication and low complexity, making it trivially reproducible by any motivated attacker.
Unauthenticated payment notification forgery in the Five Star Restaurant Reservations WordPress plugin (all versions before 2.7.23) enables remote attackers to fraudulently mark arbitrary pending reservations as paid and confirmed without completing actual payment. The plugin's payment webhook handler accepts incoming IPN-style callbacks without verifying the notification's cryptographic authenticity, recipient identity, payment amount, transaction status, or binding to a specific booking - every control that prevents payment bypass is absent. No public exploit has been identified and this vulnerability is not listed in CISA KEV, but the CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates the attack is network-accessible, requires zero privileges and zero user interaction, making it accessible to unsophisticated actors.
Unauthorized membership activation in the Simple Membership WordPress plugin (before version 4.7.7) lets unauthenticated attackers obtain paid membership access at no cost by exploiting the absence of PayPal merchant account verification during payment notification processing. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms low-complexity, unauthenticated network exploitation requiring no user interaction. No public exploit or active exploitation has been identified at time of analysis; a vendor-released patch (version 4.7.7) is available.
Server-side validation bypass in the Easy Booking WordPress plugin (all versions before 3.5.0) allows unauthenticated remote attackers to circumvent minimum booking duration enforcement during cart addition and price calculation. Malicious users can submit manipulated add-to-cart requests with durations shorter than the merchant-configured minimums, completing orders at underpriced totals that the merchant is then expected to fulfill at a financial loss. No public exploit has been identified at time of analysis, though the unauthenticated, low-complexity attack vector makes this trivially reproducible by any remote attacker with HTTP access to the affected site.
Payment fraud via forged Worldpay webhooks affects the GetPaid WordPress plugin before version 2.8.55, allowing unauthenticated remote attackers to mark pending invoices as paid without making any actual payment. The plugin fails to verify the authenticity of incoming Worldpay Instant Payment Notifications (IPNs), meaning any attacker who can reach the webhook endpoint and reconstruct a plausible notification payload can manipulate invoice status. No public exploit has been identified at time of analysis, but the business logic impact - obtaining goods or services without payment - is direct and immediately harmful to affected merchants.
WP Travel Engine WordPress plugin before 6.8.2 allows unauthenticated attackers to fraudulently mark travel bookings as fully paid by exploiting missing PayPal IPN (Instant Payment Notification) validation. The plugin neither verifies that the incoming payment notification was directed to the site's configured merchant account nor confirms that the paid amount matches the booking total, enabling attackers to complete a minimal token payment to their own PayPal account and trigger a spoofed notification that the plugin blindly accepts. With a CVSS 5.3 and no public exploit or KEV listing at time of analysis, the technical severity appears moderate, but the business impact - obtaining travel services without payment - is materially higher than the base score reflects.
Request smuggling primitive in h2 (pip/h2) versions 4.4.0 and below enables network-accessible attackers to craft HTTP/2 header blocks containing duplicate Host headers that the library forwards verbatim to consuming applications. When a consumer downgrades the HTTP/2 request to HTTP/1.1 - a common pattern in reverse proxy and gateway architectures - the resulting HTTP/1.1 request carries two Host header lines, violating RFC 7230 and creating an ambiguity that downstream servers may interpret differently, enabling cache poisoning, security control bypass, or session hijacking. No active exploitation confirmed (not in CISA KEV); no public exploit code identified at time of analysis; fix is available in v4.4.1.
Out-of-bounds heap read in the node-re2 npm package (versions <= 1.26.0) exposes up to 3 bytes of adjacent heap memory per call to JavaScript when Buffer arguments ending in a truncated multi-byte UTF-8 lead byte are passed to replace() or split(). The overread is deterministic, requires no heap grooming, and a working proof-of-concept is included in the GitHub advisory. Applications that pass only strings - not Buffers - are entirely unaffected, but those that process untrusted Buffer input through re2 are at real risk of incremental heap disclosure. No CISA KEV listing was identified; this is a library-layer flaw fixed in re2@1.26.1.
Denial-of-service in Mermaid's radar-beta diagram renderer allows an attacker who can supply diagram input to trigger unbounded CPU and memory consumption by setting the `ticks` parameter to an arbitrarily large integer. Affected npm package versions >= 11.6.0 and < 11.16.1 perform no upper-bound validation on the `ticks` value, causing the JavaScript process - whether a browser tab or a server-side renderer - to freeze indefinitely until the OS terminates it due to OOM. A proof-of-concept is publicly available in the advisory. No KEV listing exists and no EPSS score is provided.
Prototype pollution in the Mermaid JavaScript diagramming library (npm/mermaid) exposes applications to JavaScript Object prototype manipulation when attacker-controlled data is incorrectly passed to configuration APIs. The `assignWithDepth` deep-merge helper used by `mermaid.initialize`, `mermaidAPI.setConfig`, and `mermaidAPI.updateSiteConfig` fails to sanitize `__proto__` keys, allowing an attacker to corrupt the shared Object prototype if a host application forwards user-supplied input into these configuration entry points - a usage pattern explicitly outside Mermaid's documented API contract. No public exploit has been identified and no CISA KEV listing exists; vendor risk assessment is low due to the non-standard application integration pattern required for exploitation.
Unsafe method invocation via Antlers template resolution in Statamic CMS enables unauthenticated remote attackers to destroy content and stored assets on affected installations. Sites running statamic/cms below 5.74.1 or in the 6.x line below 6.24.0 are vulnerable when their templates incorporate user-supplied input into Antlers template resolution - a deployment pattern present on developer-facing or dynamic sites. No public exploit or CISA KEV listing is identified at time of analysis; the CVSS AC:H rating reflects the required site-configuration precondition, tempering real-world exposure despite the destructive impact.
User enumeration via the Statamic CMS Control Panel exposes registered email addresses to any authenticated CP user, regardless of whether they hold the 'view users' permission. The `user.exists` POST endpoint - designed for the user creation wizard - returns a boolean confirming whether a given email is registered, allowing low-privileged CP accounts to enumerate the user directory without authorization. Affected versions are composer/statamic/cms below 5.74.1 (5.x branch) and 6.0.0-6.24.0 (6.x branch); no public exploit has been identified at time of analysis.
Cross-tenant namespace disclosure in LangGraph's PostgreSQL and SQLite checkpoint stores allows an authenticated low-privileged user to read stored items belonging to other namespaces without any crafted input. The flaw arises from translating hierarchical namespaces into dot-joined strings and scoping reads with SQL LIKE patterns that have no understanding of the segment separator, so a query scoped to 'foo' also returns data from 'foobar' or 'foo2'. Exploitation requires the specific precondition of prefix-overlapping or wildcard-containing namespace labels; no public exploit code exists and the vendor confirms no evidence of in-the-wild exploitation.
Timing side-channel exposure in Apache Portable Runtime Utility (APR-util) versions 1.2.0 through 1.6.3 allows network-accessible attackers to statistically recover passwords or hashes by measuring response-time variance in the `apr_password_validate()` function, which performs non-constant-time comparisons. The risk is materially elevated on platforms lacking native `crypt()` support - specifically Windows, Android, BeOS, and NetWare - where the non-constant-time code path is always exercised rather than conditionally. No public exploit has been identified at time of analysis, though the SSVC framework assesses the attack as automatable with partial technical impact.
Sensitive data exposure in the Gutenberg Blocks by Kadence Blocks WordPress plugin (versions <= 3.7.8) allows authenticated Contributor-level users to access information they should not be permitted to view. The CVSS vector (PR:L/C:L) confirms this is a low-privilege, partial confidentiality breach rather than a full data dump, limiting its severity to medium-low. No public exploit code has been identified and CISA KEV does not list this vulnerability, indicating no confirmed active exploitation at time of analysis.
Unauthenticated sensitive data exposure in the Featured Video Plus WordPress plugin (versions <= 2.3.3) allows any remote attacker to retrieve sensitive information without credentials via a crafted network request. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms this is exploitable against any default installation of the plugin with no prerequisites beyond network access. Classified under CWE-201, the plugin inserts sensitive information into its sent data, making it passively harvestable. No public exploit code or CISA KEV listing has been identified at time of analysis.
Unauthenticated sensitive data exposure in the Export Import Menus WordPress plugin (versions up to and including 1.9.2) allows remote, unauthenticated attackers to access sensitive information by invoking the plugin's export functionality without any credentials. Classified under CWE-201 (Insertion of Sensitive Information Into Sent Data), the plugin returns sensitive data in its HTTP responses to unauthenticated requests. No public exploit code has been identified at time of analysis, and this CVE does not appear on the CISA Known Exploited Vulnerabilities catalog.
Unauthenticated sensitive data exposure in the Custom CSS and JavaScript WordPress plugin (by WP Zone) versions up to and including 2.0.16 allows remote unauthenticated attackers to read sensitive information via network-accessible endpoints. Classified under CWE-201 (Insertion of Sensitive Information Into Sent Data), the flaw permits retrieval of data that the plugin transmits without requiring any authentication, with a CVSS 3.1 score of 5.3 (Medium). No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
Broken authentication in WP Event Solution WordPress plugin (versions ≤4.1.9) permits unauthenticated remote attackers to bypass authentication controls via an alternate path or channel (CWE-288), resulting in limited information disclosure and partial integrity impact. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms this is exploitable over the network with no credentials and no user interaction required against any WordPress installation running the affected plugin. No public exploit code and no CISA KEV listing have been identified at time of analysis.
Broken Authentication in Gutena Forms WordPress plugin (versions <= 1.9.0) allows unauthenticated remote attackers to bypass authentication controls, resulting in limited integrity and availability impacts against form configurations or submissions. The vulnerability is classified as CWE-288 (Authentication Bypass Using an Alternate Path or Channel) and was reported by Patchstack. No public exploit code or CISA KEV listing has been identified at time of analysis, but the low attack complexity and lack of authentication requirements make it straightforward to attempt against any exposed WordPress installation running the affected plugin.
Unauthenticated sensitive data exposure in the YITH WooCommerce Zoom Magnifier WordPress plugin (versions ≤ 2.52.0) permits remote, unauthenticated attackers to retrieve sensitive information without any credentials. Classified under CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere), the plugin exposes data through a network-accessible endpoint that lacks proper authorization controls. No public exploit code and no CISA KEV listing have been identified at time of analysis, though the low attack complexity makes opportunistic discovery straightforward.
RealHomes Memberships WordPress plugin before 3.1.0 permits any authenticated user - including low-privilege Subscribers - to claim paid membership packages for free by exploiting missing payment verification, absent nonce validation, and no capability checks on the membership grant endpoint. The business impact is direct financial loss for site operators running paid real estate membership tiers. No active exploitation has been confirmed by CISA KEV, but a public exploit is available via WPScan, lowering the barrier for abuse.
Business logic enforcement failure in WonderTrader's backtesting engine (versions up to 0.9.9) allows a low-privileged authenticated remote attacker to manipulate the internal limit order book cache through the MatchEngine::update_lob function in src/WtBtCore/MatchEngine.cpp. The flaw enables integrity-affecting manipulation of simulated or processed order book state in violation of expected matching workflow constraints. No vendor patch exists - the vendor did not respond to responsible disclosure - and proof-of-concept exploit code is publicly available (CVSS 4.0 E:P), though real-world risk is substantially bounded by the authentication requirement, low-only integrity impact, and niche deployment footprint.
Local privilege abuse in pardus-domain-joiner (TÜBİTAK BİLGEM Software Technologies Research Institute) before version 0.5.5 exposes Pardus Linux systems to unauthorized resource access through unverified ownership checks (CWE-283). A locally authenticated user with low privileges can trigger a code path where ownership of a resource is not validated before access or privileged operations are permitted, enabling privilege abuse. No public exploit code or active exploitation has been identified; the CVSS score of 3.3 reflects limited real-world impact confined to local sessions on Pardus Linux systems.
Improper input validation in OMICRON StationGuard 4.00 allows an adjacent network attacker to crash the IEC 61850 Sampled Values processing component by sending a specially crafted SV frame. The disruption is self-healing - the process restarts automatically and the failure is immediately surfaced to operators - leaving overall system availability and all other monitored traffic types unaffected. No public exploit code exists and this vulnerability is not listed in CISA KEV; the CVSS 4.0 score of 1.3 reflects the accurately bounded, minimal real-world impact.
openvpnserv on Windows insufficiently validates command line arguments received from its control socket before passing them to the openvpn.exe process, allowing a low-privileged local user to circumvent administrator-defined restrictions on permitted OpenVPN configuration directories. Affected installations span OpenVPN 2.4.0 through 2.6.21 and 2.7_alpha1 through 2.7.5 on Windows; fixed releases 2.6.22 and 2.7.6 shipped August 5, 2026. No public exploit or CISA KEV listing has been identified at time of analysis, though the CVSS 4.0 SC:H metric indicates that bypassing config directory controls could allow rogue VPN configurations to be loaded, with high downstream confidentiality impact on subsequent network systems.
Certificate validation bypass in OpenVPN 2.7 alpha series (mbedTLS builds) causes the --x509-username-field directive to unintentionally accept certificates that should be rejected, potentially granting unauthorized VPN network access. Only deployments running a 2.7 alpha or pre-release build compiled against mbedTLS and explicitly configured with --x509-username-field are exposed; OpenVPN 2.6.x stable series and OpenSSL-backend builds are not affected. The vendor characterizes this as a low-priority security finding; no public exploit has been identified at time of analysis and it is not listed in the CISA Known Exploited Vulnerabilities catalog.
eta-otp-lock before version 1.0.4 exposes sensitive information - likely OTP codes or credentials - as visible process arguments during invocation, enabling local system footprinting by other users. The vulnerability maps to CWE-214, where secrets passed via command-line arguments or process environment can be read by any local user through standard OS interfaces such as /proc or ps. No public exploit code exists and the product is not listed in CISA KEV, but the high confidentiality impact reflects the sensitivity of OTP material if intercepted.
Tenant isolation failure in WSO2 Identity Server allows authenticated low-privilege users to disclose personally identifiable information belonging to users in separate tenants. The vulnerability exists specifically when Email OTP, SMS OTP, or Magic Link are configured as first-factor authenticators - authentication requests processed through these flows lack sufficient validation to enforce organizational tenant boundaries, exposing data such as mobile numbers. No public exploit code or CISA KEV listing exists at time of analysis, but the low-complexity, network-accessible attack vector (CVSS PR:L/AV:N/AC:L) makes this a credible insider threat and compromised-account scenario for multi-tenant deployments.
Insufficient refresh token invalidation in WSO2 Identity Server's user impersonation flow allows a privileged attacker who has already obtained an impersonated access token to silently renew that authorization via the OAuth refresh token grant, sustaining unauthorized access well beyond the intended session lifetime. The integrity impact is two-fold: the attacker continues performing actions on behalf of the legitimate user, and audit logs attribute those actions to the victim identity rather than the true actor, corrupting traceability and compliance posture. No public exploit is identified and exploitation is bounded by high privilege prerequisites (PR:H) and adjacent network access (AV:A), placing realistic risk firmly in insider-threat and compromised-administrator scenarios.
Cross-organizational secret deletion in WSO2 Identity Server's Secret Type Management REST API allows an administrator with delete permissions to inadvertently remove secrets across all organizations in a multi-tenant deployment. The on-delete cascade logic, triggered when a secret type is deleted, fails to enforce organizational boundaries - a multi-tenancy isolation failure classified as CWE-281 (Improper Preservation of Permissions). Exploitation yields availability and integrity impact across the entire deployment, though it is constrained to high-privilege administrator accounts. No public exploit is identified and this vulnerability is not listed in the CISA KEV catalog.
Username enumeration via observable login response discrepancy affects WSO2 Identity Server, WSO2 Identity Server as Key Manager, WSO2 API Manager, WSO2 Open Banking AM, and WSO2 Open Banking IAM when the Multi-Attribute Login feature is enabled. When a valid username is submitted, the server resolves and returns the canonical form of that username; when an invalid username is submitted, the server echoes the raw input unchanged - creating a deterministic, scriptable oracle for account existence. This disclosure path persists regardless of the validate_username configuration setting, meaning a common hardening measure provides no defense. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
Incomplete session cleanup in poco-ai/poco-agent up to version 0.5.4 can permanently destroy the host user's ~/.claude directory - including all Claude Code chat history stored under ~/.claude/projects - when the agent runs outside a container environment. The WorkspaceManager._setup_session_persistence method performs an unconditional rmtree followed by a symlink swap on ~/.claude without verifying a container context, and the corresponding cleanup phase can additionally unlink pre-existing ~/.claude symlinks unrelated to poco-agent. A publicly available exploit exists via GitHub issue #131 and PR #132, though the CVSS 4.0 base score of 2.9 reflects high attack complexity and impact limited to low integrity and availability loss with no confidentiality breach.
File inclusion in TinyAGI 0.0.20 exposes server-side files to remote unauthenticated attackers through the buildSystemPrompt function in packages/server/src/routes/agents.ts. Exploitation requires no privileges or user interaction, and a publicly available proof-of-concept exists via GitHub issue #283. No patch has been released - the vendor has not responded to the responsible disclosure despite being notified through the project's issue tracker.
In the Linux kernel, the following vulnerability has been resolved: iio: adc: spear: Initialize completion before requesting IRQ In the report from Jaeyoung Chung: "spear_adc_probe() in drivers/iio/adc/spear_adc.c registers its interrupt handler with devm_request_irq() before it initializes st->completion with init_completion(). If an interrupt arrives after devm_request_irq() and before init_completion(), the handler calls complete() on an uninitialized completion, causing a kernel panic. The probe path, in spear_adc_probe(): iodev = devm_iio_device_alloc(&pdev->dev, sizeof(*st)); /* st kzalloc-zeroed */ ... retval = devm_request_irq(&pdev->dev, irq, spear_adc_isr, 0, LPC32XXAD_NAME, st); /* register handler */ ... init_completion(&st->completion); /* initialize completion */ spear_adc_isr() calls complete(): complete(&st->completion); If the device raises an interrupt before init_completion() runs, complete() acquires the uninitialized wait.lock and walks the zeroed task_list in swake_up_locked(). The zeroed task_list makes list_empty() return false, so swake_up_locked() dereferences a NULL list entry, triggering a KASAN wild-memory-access." Fix the chance of a spurious IRQ causing an uninitialized pointer dereference by moving init_completion() above devm_request_irq().
In the Linux kernel, the following vulnerability has been resolved: HID: hid-lenovo-go: cancel cfg_setup work in hid_go_cfg_remove() hid_go_cfg_probe() initialises drvdata.go_cfg_setup and schedules it to run 2 ms later: INIT_DELAYED_WORK(&drvdata.go_cfg_setup, &cfg_setup); schedule_delayed_work(&drvdata.go_cfg_setup, msecs_to_jiffies(2)); cfg_setup() dereferences drvdata.hdev to issue MCU command requests. hid_go_cfg_remove() tears down sysfs and stops the HID device, but never drains the delayed work. If the device is unbound within the 2 ms scheduling delay (a probe failure rolling back via remove, or a fast rmmod after probe), the work fires after hid_destroy_device() has dropped its reference and released the underlying hdev struct, leaving cfg_setup() with a stale drvdata.hdev pointer. Mirror the sibling driver hid-lenovo-go-s.c, whose hid_gos_cfg_remove() already calls cancel_delayed_work_sync() on its analogous work, and drain go_cfg_setup at the top of hid_go_cfg_remove(). The cancel must come before guard(mutex)(&drvdata.cfg_mutex) because cfg_setup() acquires that mutex; reversing the order would deadlock.
In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_fs: initialize reset_work at allocation time ffs_fs_kill_sb() unconditionally calls cancel_work_sync() on ffs->reset_work when a functionfs instance is unmounted: ffs_data_reset(ffs); cancel_work_sync(&ffs->reset_work); However ffs->reset_work is only ever initialized via INIT_WORK() in ffs_func_set_alt() and ffs_func_disable(), and only on the FFS_DEACTIVATED path. That state is reached solely by ffs_data_closed() when the instance is mounted with the "no_disconnect" option, so for the common case (no "no_disconnect", or mounted and unmounted without ever being deactivated) reset_work is never initialized. ffs_data_new() allocates the ffs_data with kzalloc_obj() and does not initialize reset_work, and ffs_data_reset()/ffs_data_clear() do not touch it either, so reset_work.func is left NULL. cancel_work_sync() on such a work then trips the WARN_ON(!work->func) guard in __flush_work(): WARNING: kernel/workqueue.c:4301 at __flush_work+0x330/0x360, CPU#3: umount Call trace: __flush_work cancel_work_sync ffs_fs_kill_sb [usb_f_fs] deactivate_locked_super deactivate_super cleanup_mnt __cleanup_mnt task_work_run exit_to_user_mode_loop el0_svc On older kernels cancel_work_sync() on a zero-initialized work struct was a silent no-op, which hid the missing initialization. Initialize reset_work once in ffs_data_new() so it is always valid for the lifetime of the ffs_data, and drop the now-redundant INIT_WORK() calls from the two deactivation paths.
In the Linux kernel, the following vulnerability has been resolved: dma-buf/udmabuf: skip redundant cpu sync to fix cacheline EEXIST warning When CONFIG_DMA_API_DEBUG_SG is enabled, importing a udmabuf into a DRM driver (e.g. amdgpu for video playback in GNOME Videos / Showtime) triggers a spurious warning: DMA-API: amdgpu 0000:03:00.0: cacheline tracking EEXIST, \ overlapping mappings aren't supported WARNING: kernel/dma/debug.c:619 at add_dma_entry+0x473/0x5f0 The call chain is: amdgpu_cs_ioctl -> amdgpu_ttm_backend_bind -> dma_buf_map_attachment -> [udmabuf] map_udmabuf -> get_sg_table -> dma_map_sgtable(dev, sg, direction, 0) // attrs=0 -> debug_dma_map_sg -> add_dma_entry -> EEXIST This happens because udmabuf builds a per-page scatter-gather list via sg_set_folio(). When begin_cpu_udmabuf() has already created an sg table mapped for the misc device, and an importer such as amdgpu maps the same pages for its own device via map_udmabuf(), the DMA debug infrastructure sees two active mappings whose physical addresses share cacheline boundaries and warns about the overlap. The DMA_ATTR_SKIP_CPU_SYNC flag suppresses this check in add_dma_entry() because it signals that no CPU cache maintenance is performed at map/unmap time, making the cacheline overlap harmless. All other major dma-buf exporters already pass this flag: - drm_gem_map_dma_buf() passes DMA_ATTR_SKIP_CPU_SYNC - amdgpu_dma_buf_map() passes DMA_ATTR_SKIP_CPU_SYNC The CPU sync at map/unmap time is also redundant for udmabuf: begin_cpu_udmabuf() and end_cpu_udmabuf() already perform explicit cache synchronization via dma_sync_sgtable_for_cpu/device() when CPU access is requested through the dma-buf interface. Pass DMA_ATTR_SKIP_CPU_SYNC to dma_map_sgtable() and dma_unmap_sgtable() in udmabuf to suppress the spurious warning and skip the redundant sync.
In the Linux kernel, the following vulnerability has been resolved: i2c: core: fix NULL-deref on adapter registration failure If adapter registration ever fails the release callback would trigger a NULL-pointer dereference as the completion struct has not been initialised. Note that before the offending commit this would instead have resulted in a minor memory leak of the adapter name.
File inclusion via unsanitized path input in TinyAGI 0.0.20's Message API Endpoint exposes server-side files to remote unauthenticated attackers. The vulnerable surface is the `collectFiles` function in `packages/core/src/response.ts`, which accepts externally controlled file paths without adequate validation (CWE-73). Publicly available exploit code exists via GitHub issue #282, and the project maintainer had not issued a patch or response at time of disclosure - compounding risk for any internet-exposed deployments.
Symlink escape in openclaw-cn's apply_patch Tool allows authenticated remote attackers on versions up to 0.2.1 to traverse outside the intended sandbox boundary by exploiting a failure in the assertNoSymlinkEscape validation function in src/agents/sandbox-paths.ts. Attackers with low-level access can craft symbolic links within the sandbox that resolve to paths outside it, yielding limited unauthorized read and write access to the underlying filesystem. A public proof-of-concept exploit is documented in GitHub issue #566, and no vendor patch has been released as the project has not responded to disclosure.
Cleartext exposure of third-party API keys and authentication tokens in AI Engine WordPress plugin (before 3.6.4) allows Editor-role users to read secrets that are intended to be administrator-only. The plugin inlines sensitive configuration values into admin page JavaScript without redaction, making them readable to any authenticated user with Editor access who inspects the page source. A public proof-of-concept exists per WPScan, though EPSS remains low at 0.17% (7th percentile) and the vulnerability is not in the CISA KEV catalog.
tourmaster WordPress plugin (all versions before 5.4.9) exposes exported customer booking and order data via a fixed, predictable file path inside its publicly accessible web directory, with no authentication or access control enforcing download restrictions. Any unauthenticated network attacker who knows or can derive the static export file URL can retrieve personally identifiable information - names, contact details, and booking records - after an administrator has triggered an export. A publicly available proof-of-concept exists per WPScan, and exploitation is fully automatable (SSVC), though EPSS sits at 0.14% and no CISA KEV listing exists at time of analysis.
Unauthorized retrieval of other customers' payment receipt images is possible in PeproDev WooCommerce Receipt Uploader (≤ 2.8.0) because the plugin's token-based attachment access mechanism never validates that a requested attachment ID belongs to the order the token was issued for. Unauthenticated network attackers can forge or repurpose a token - trivially obtained by placing any order - to iterate over attachment IDs and exfiltrate payment receipts uploaded by unrelated customers, potentially exposing financial documents containing banking details or PII. A publicly available proof-of-concept exists per WPScan reporting (EUVD-2026-53719); no CISA KEV listing indicates widespread active exploitation has not been confirmed, though SSVC rates the attack as automatable.
Incorrect privilege assignment in cosmicstack-labs mercury-agent (all versions through 1.1.12) allows authenticated remote attackers to bypass shell command permission checks via the run_command Handler. The flaw resides in the PermissionManager.checkShellCommand function within src/capabilities/permissions.ts, where privilege levels are not correctly validated, potentially enabling a low-privileged user to execute shell commands exceeding their authorized scope. A public proof-of-concept exploit exists via GitHub issue #72, and the project maintainer has not responded to responsible disclosure, leaving no vendor-released patch available at time of analysis.
Information disclosure in netease-youdao LobsterAI 2026.6.10 exposes sensitive data through manipulation of the MEDIA Path Handler component. The vulnerable function parseMediaTokensFromText in src/renderer/services/artifactParser.ts can be triggered remotely when a user interacts with attacker-controlled content, leaking confidential information such as local file system paths or internal metadata. A publicly available exploit exists via GitHub issue #2176, and the vendor has not responded to coordinated disclosure, leaving no patch available at time of analysis.
Incorrect privilege assignment in NousResearch hermes-agent through 0.16.0 allows authenticated remote users to invoke toolsets that administrators have explicitly disabled via the disabled_toolsets configuration. The flaw resides in get_tool_definitions within agent/agent_init.py, where the disabled_toolsets list was not checked before injecting tool definitions into an agent session, causing disabled tools (e.g., 'memory') to remain fully accessible. No active exploitation is confirmed (not in CISA KEV), but a public proof-of-concept exists via GitHub issue #46171 and an upstream fix is available in PR #46185.
Unauthenticated remote information disclosure in heshengtao super-agent-party (up to version 0.4.1) allows remote attackers to read sensitive file content by manipulating the tool_name or tool_params arguments passed to the get_file_content function via the execute_tool_manually endpoint in server.py. The flaw requires no authentication and no user interaction, and a public proof-of-concept exploit is available on GitHub. No patch has been issued; the vendor did not respond to coordinated disclosure.
Out-of-bounds heap read in HDF5's N-Bit filter decompression affects all versions through 2.3.0, allowing an attacker who can deliver a crafted HDF5 file to a user or automated pipeline to trigger application crashes and, in constrained cases, leak adjacent heap memory contents into decompressed dataset values. The three affected functions - H5Z__nbit_decompress_one_byte, H5Z__nbit_decompress_one_nooptype, and H5Z__nbit_decompress_one_atomic - advance a buffer read index without bounding it against the actual compressed chunk size, exploitable whenever H5Dread is invoked, including via common tools like h5ls and h5repack. No public exploit code has been identified at time of analysis, and this vulnerability is not listed in the CISA KEV catalog.
Unauthorized component instantiation in Nuxt server islands (versions >=3.1.0 <3.21.10 and >=4.0.0 <4.5.1) allows remote unauthenticated attackers to render arbitrary globally-registered Vue components or native HTML elements - including constructs like `<iframe>` - by supplying a crafted string prop to the `/__nuxt_island/` endpoint. The attack exploits Vue's attribute fallthrough behavior: props an island does not declare pass through to its root element, so if that root is a polymorphic component (such as reka-ui or @nuxt/ui elements using an `as` prop), the attacker's string silently reaches dynamic component resolution without any explicit forwarding in the island author's code. Unlike the related RCE vector GHSA-9473-5f9j-94wq, this does not require `vue.runtimeCompiler`, making it reachable in substantially more configurations; however, no public exploit has been identified at time of analysis and real-world exploitation is constrained by application-specific island configuration requirements.
Credential exposure in HCL Digital Experience and Digital Experience Compose allows sensitive authentication material to be written to web server logs under specific, non-default configurations when the default login portlet is in use. The flaw, classed as CWE-522 (Insufficiently Protected Credentials), means that any party with read access to web server logs - such as operations staff, log aggregation systems, or an attacker who has compromised a log pipeline - may recover cleartext or weakly protected user credentials. No public exploit code has been identified at time of analysis, and active exploitation has not been confirmed by CISA KEV.
Authenticated users in IBM Langflow OSS 1.0.0 through 1.10.3 can exploit a privileged built-in component to read arbitrary server-side environment variables, bypassing security controls designed to restrict custom component execution. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H) confirms this is a low-complexity, network-accessible flaw requiring only standard user credentials, with high confidentiality impact. No active exploitation confirmed via CISA KEV, and no public exploit code has been identified at time of analysis; IBM has released a patch via its support portal.
Prototype pollution via Electron's contextBridge allows untrusted renderer-side web content to smuggle a malicious prototype across the isolation boundary into preload script context, bypassing context isolation in versions prior to 39.8.9, 40.9.2, 41.2.2, and 42.0.0-beta.4. Exploitation is conditional on preload scripts accepting object arguments from untrusted content and reading inherited properties without own-property guards. No public exploit has been identified at time of analysis, and the flaw is not listed in CISA KEV; however, the scope-change (S:C) CVSS metric reflects that a successful attack crosses the renderer-to-preload privilege boundary, which can have amplified consequences in apps that expose sensitive Node.js APIs through the bridge.
Credential exposure in Cisco RoomOS allows an authenticated low-privilege local user to capture user login credentials by enabling a specific debug logging level and collecting the resulting system logs. The flaw (CWE-532) spans a wide version range from RoomOS 10.x through 26.x across Cisco's entire room collaboration device portfolio. No public exploit code has been identified and this CVE does not appear in the CISA KEV catalog at time of analysis, but the High confidentiality impact - plaintext credential disclosure - warrants prioritized patching on any device with non-administrative local accounts.
Cleartext credential exposure in Cisco Catalyst SD-WAN Manager's web-based management interface allows an authenticated low-privileged remote attacker to read sensitive authentication material from system logs. The root cause is an incomplete encryption allowlist: specific template types are excluded from the encryption policy, resulting in sensitive values being written to logs in cleartext - accessible both on the local system and on any configured remote logging server. No public exploit code has been identified and this vulnerability is not listed in CISA KEV, but successful exploitation directly enables credential theft that can cascade into broader SD-WAN infrastructure compromise.
Privilege escalation via command injection in Cisco Integrated Management Controller (IMC) allows authenticated Admin-level attackers to execute arbitrary OS commands and elevate to root on affected Cisco UCS Standalone and E-Series systems. Exploitation requires Admin credentials to the web-based management interface but results in full OS root access, which Cisco rates as High SIR despite a CVSS 6.5 (Medium) score - explicitly noting that root attainment carries security implications beyond what the base score reflects. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis.
Electron's window.open() features string parsing forwards untrusted BrowserWindowConstructorOptions directly to child BrowserWindows without an allowlist, allowing renderer-side web content to supply privileged options - such as icon - that cause the trusted main process to access attacker-chosen file or network paths. All Electron apps serving untrusted web content without a setWindowOpenHandler guard are affected across the 39.x, 40.x, 41.x, and 42.x beta series. No public exploit code has been identified and this vulnerability is not listed in the CISA KEV catalog; the practical attack surface is narrowed to apps that load third-party or user-controlled content and omit the recommended setWindowOpenHandler override.
Bolt protocol handshake decoder in Neo4j Enterprise and Community Editions fails to distinguish overlong capability masks from truncated ones, leaving server-side channels permanently open without producing a finalization message. Any unauthenticated client reaching the Bolt connector (default TCP 7687) can trigger this pre-authentication stall by sending 32 continuation bytes in the capability mask, causing the decoder to loop on the same unread bytes. The CVSS 4.0 vector carries E:P (proof of concept exists) with a low availability impact; no active exploitation has been confirmed via CISA KEV, but the trivial pre-auth trigger and POC availability increase realistic risk to exposed Bolt endpoints.
Session isolation bypass in Electron's custom protocol handler allows cached HTTP responses from defaultSession to leak across otherwise isolated session partitions. Electron versions 40.x through pre-release 43.x are affected when apps use ProtocolResponse.url without specifying ProtocolResponse.session, causing upstream requests to be routed through defaultSession regardless of which session registered the protocol handler. An attacker who can trigger a cross-session cache hit may read confidential session-scoped content (C:H) or partially influence cached responses (I:L) intended for a different, isolated session; no public exploit or CISA KEV listing exists at time of analysis.
IBM Maximo Application Suite 9.0, 9.1, and 9.2 fails to set the `Secure` attribute on authorization tokens and session cookies, enabling interception of credential material over unencrypted HTTP. An attacker who tricks an authenticated user into following an HTTP link - via phishing or a malicious page - causes the victim's browser to transmit the session cookie in plaintext, where it can be captured by a server the attacker controls or via network sniffing. No public exploit has been identified at time of analysis and the vulnerability is not listed in the CISA KEV catalog; however, session token theft can lead to full account takeover, meaningfully exceeding the limited confidentiality scope implied by the raw CVSS score.
Session data tampering in IBM Maximo Application Suite 9.0, 9.1, and 9.2 is possible because the application signs session tokens with a weak HMAC secret, classified under CWE-330 (Use of Insufficiently Random Values). A remote unauthenticated attacker who can derive or predict the HMAC signing key may forge or modify session tokens, undermining session integrity across affected deployments. No public exploit code has been identified, this vulnerability is not listed in the CISA KEV catalog, and a vendor patch is available via IBM's advisory.
Improper TLS hostname verification in IBM Business Automation Workflow exposes high-privilege sessions to man-in-the-middle interception by failing to validate that server certificates match the target hostname. Affected deployments span both containerized (Kubernetes/OpenShift) and traditional on-premises models across multiple release trains from 24.0.0 through 26.0.0. No public exploit has been identified and the vulnerability is not listed in CISA KEV; real-world risk is substantially bounded by the PR:H requirement - an attacker must already hold administrative credentials before exploitation is feasible.
Unauthenticated remote information disclosure in IBM Cloud Pak for Business Automation 24.0.0 through 26.0.0 allows network attackers to retrieve sensitive data embedded in externally accessible manifest files. The vulnerability stems from CWE-538, where sensitive configuration or operational data is written into manifest files that are not adequately protected from external access. No public exploit has been identified at time of analysis, and a vendor patch is available via IBM's support portal.
Electron's permission check handler incorrectly exposes cross-origin iframes to unauthorized camera, microphone, and serial port access by passing the top-level frame's origin as `requestingOrigin` instead of the requesting iframe's own origin. Applications implementing `session.setPermissionCheckHandler` with origin-based grant logic that also embed cross-origin iframes with delegated device permissions are affected - the handler is deceived into approving the iframe's request as if it came from the trusted top-level origin. No public exploit code exists and CISA KEV listing is not confirmed; the CVSS score of 5.9 with AC:H accurately reflects the specific multi-condition deployment pattern required for exploitation.
Out-of-bounds memory read in Electron's offscreen rendering pipeline allows a compromised GPU process to cause the browser/main process to read beyond a shared memory mapping boundary when producing `paint` event images, disclosing process memory or crashing the application. Exploitation requires two independent preconditions: the host application must enable `webPreferences.offscreen` (non-default) and an attacker must have already achieved code execution in the GPU process via a separate vulnerability. No public exploit code has been identified at time of analysis, and this vulnerability is not listed in the CISA KEV catalog.
Arbitrary file write via crafted tar archive extraction in Jenkins 2.575 and earlier allows attackers controlling agent processes to escape extraction directory boundaries on the controller filesystem, directly enabling remote code execution. The root cause is unsafe handling of symbolic links with effectively empty names during .tar and .tar.gz extraction on the controller, permitting writes to sensitive paths such as JENKINS_HOME/init.groovy.d/ (Groovy init scripts) or JENKINS_HOME/plugins/ (plugin deployment). No public exploit or CISA KEV listing has been identified at time of analysis, but the agent-to-controller trust boundary is a well-established Jenkins attack surface with a history of critical exploitation.
Remote code execution and privilege escalation across Jenkins core and multiple plugins were disclosed in the 2026-08-05 security advisory, with the most critical issue being a JEP-200 deserialization filter bypass (CVE-2026-70426) in Remoting 3384.v60d89463d9e0 and earlier that allows agent processes or holders of Agent/Connect permission to execute arbitrary code on the Jenkins controller. Compounding this, two separate arbitrary file-write primitives (CVE-2026-70427 via malicious tar archives, CVE-2026-70428 via path traversal in file parameter names) independently enable code execution by writing into JENKINS_HOME/init.groovy.d/ or deploying rogue plugins. No public exploit code or CISA KEV listing was identified at time of analysis, but the attack surface spans both network-accessible agents and authenticated users with low-privilege build permissions.