Information Disclosure
Monthly
Command injection and arbitrary file truncation in the Perl GD module before 2.86 (perl-gd 2.86-r0 on Alpine) arise because GD::Image's _make_filehandle helper opened filenames using Perl's two-argument open(). When an application passes an attacker-influenced filename to constructors like GD::Image->new or newFrom*, prefixes such as `cmd |`, `| cmd`, or `> file` are interpreted by Perl as a command pipe or redirect, yielding command execution or destructive file truncation. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV; EPSS is 0.26% (50th percentile).
Qt6 WebEngine (qt6-qtwebengine) on Alpine Linux has been patched in package version 6.10.1-r7, addressing an unspecified vulnerability. The nature, severity, and exploitability of the underlying flaw are not disclosed in available intelligence - no CVE description, CVSS score, CWE classification, or vendor advisory narrative has been published at time of analysis. Alpine Linux is the sole reporting source, and the fix is confirmed present in the Alpine package repository at version 6.10.1-r7.
Active exploitation confirmed by CISA KEV affects qt6-qtwebengine on Alpine Linux, with the vulnerability addressed in package version 6.9.1-r3. The specific vulnerability class and technical mechanism are not disclosed in available intelligence - the only confirmed data point beyond KEV status is the Alpine Linux package fix designation. Despite CISA KEV confirmation, the EPSS score of 0.25% (49th percentile) is notably low, indicating exploitation is targeted rather than widespread or automated. Any application or system running Alpine Linux with qt6-qtwebengine prior to 6.9.1-r3 should be treated as at risk given the confirmed exploitation status.
Integer underflow (CWE-191) in Netatalk, the open-source Apple Filing Protocol (AFP) server, allows a network-authenticated attacker to trigger memory corruption that may result in information disclosure, arbitrary code execution, or denial of service. The vulnerability affects versions prior to 4.4.3 and is patched in Netatalk 4.4.3 (Alpine Linux package 4.4.3-r0). No public exploit code or active exploitation via CISA KEV has been identified at time of analysis.
Confirmed actively exploited vulnerability in qt6-qtwebengine on Alpine Linux has been patched in package version 6.10.1-r2. Qt6 WebEngine is a Chromium-based web content rendering component embedded in Qt6 applications; vulnerabilities in this component typically affect any application that renders untrusted web content. Despite CISA KEV confirmation of active exploitation, the EPSS score of 0.30% (53rd percentile) suggests exploitation has been targeted rather than widespread, warranting urgent patching prioritization nonetheless.
Netatalk on Alpine Linux contains an unspecified vulnerability addressed by the Alpine package maintainers in version 4.4.3-r0. The nature of the flaw, affected attack surface, and impact have not been disclosed in the available intelligence - the sole data point is the vendor-issued Alpine Linux package fix. Security teams should treat this as a pending-disclosure patch event and apply the update while awaiting a full CVE write-up.
JWT signature verification weakness in the Cacti network monitoring framework (fixed in 1.2.31) lets an authenticated low-privilege user forge or tamper with JSON Web Tokens whose signatures are not properly validated, undermining token integrity. The CWE-347 root cause combined with the vendor's 'Jwt Attack' and 'Information Disclosure' tags points to token forgery that can bypass intended authorization checks. There is no public exploit identified at time of analysis and the flaw is not listed in CISA KEV; it was reported through the Alpine Linux vendor channel and patched upstream by the Cacti project.
Client-side memory corruption in FreeRDP (all versions before 3.27.1) lets a malicious or compromised RDP server compromise a connecting client through improperly bounds-checked bitmap cache orders. The cacheId field of Cache Bitmap V2/V3 orders was masked to only two bits (0x0003) instead of three (0x0007) and used to index cell-cache arrays without validating it against the negotiated number of cells, enabling out-of-bounds access controlled by the server. There is no public exploit identified at time of analysis and EPSS is low (0.45%, 36th percentile), but the CVSS 8.8 reflects full confidentiality, integrity and availability impact once a user connects to the attacker's server.
Trailing whitespace at the end of a selector string makes Dasel 3.0.0 through 3.11.1 read past the end of its input and panic with an index-out-of-range error, terminating the process - an availability-only denial of service. The trigger is trivially small (dasel query 'a ', or a selector ending in a tab or newline) and is reachable both from the command line and from the Go library entry points dasel.Query and lexer.NewTokenizer(...).Tokenize(), so any embedding application that forwards caller-influenced selector text into Dasel can be crashed. The assessed impact is local and unauthenticated with high availability impact and no confidentiality or integrity effect (CVSS 6.2), no public exploit code was identified at time of analysis, and version 3.11.2 is the fixed release.
Username enumeration is possible against Tinyauth instances running versions before 5.1.0 because the local-user login handler and the HTTP basic-auth middleware return as soon as an account is reported missing, while an existing account triggers a comparatively slow bcrypt password verification, leaving a remotely measurable timing discrepancy (CWE-208). Unauthenticated attackers with network reach to the authentication endpoints can take repeated latency measurements and statistically distinguish valid local usernames from invalid ones; the independent assessment rates this CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N, so the outcome is limited to disclosure of valid usernames with no direct password, session, or data compromise, and exploitation is constrained by network/server jitter requiring many samples. Deployments that authenticate exclusively through external OAuth/OIDC providers and maintain no local users do not exercise the vulnerable bcrypt path, and no public exploit code was identified at time of analysis; the vendor-released fix is version 5.1.0.
Authenticated, low-privileged users of GoCD before 26.1.0 can retrieve source-control credentials in cleartext from several read-only pipeline and material APIs whose responses fail to mask the userinfo portion of material URLs. Exposure is narrow: it only affects legacy configurations where an administrator embedded a username and password directly in a material URL, while credentials held in GoCD's dedicated password fields or secret-management plugins stay encrypted and are not disclosed by this issue. The CVSS 4.0 base score of 2.3 reflects the uncommon prerequisite configuration (AT:P) and limited confidentiality impact, and no public exploit code or confirmed active exploitation has been identified at time of analysis.
Logout in Apache Airflow Core API versions before 3.3.2 silently fails to revoke the caller's credential when it is presented as an `Authorization: Bearer` header rather than the browser `_token` session cookie, returning a normal logout response while nothing is invalidated. The token therefore stays usable until its natural expiry, 24 hours by default and configurable, so an authenticated attacker who already holds a copy of that token keeps the victim's access after the victim has logged out and believes the session ended; no privileges beyond the victim's own are obtained and obtaining the token is outside the scope of this issue. There is no public exploit identified at time of analysis and no confirmed active exploitation - the flaw is assessed as low severity (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N) precisely because it is strictly gated on the attacker already possessing a valid token that this endpoint cannot mint or steal.
Information disclosure in Apache Airflow's `/assets/events` REST endpoint lets an authenticated user who holds asset-read permission enumerate asset events - source Dag ID, task ID, run ID, timestamps, and total existence counts via pagination - for Dags they have no authorization to read. The endpoint applied no per-Dag readability filter, and because the same filter was missing from the count query, `total_entries` alone revealed the existence of hidden Dags. Affected deployments are apache-airflow versions prior to 3.3.2, and the exposure matters only where per-Dag access control is used to separate teams or tenants; in single-tenant deployments every user is already authorized to see all Dags, so nothing new is disclosed. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (CISA KEV), so this is a modest-severity broken-authorization flaw rather than a high-urgency issue. Vendor-released patch: apache-airflow 3.3.2.
MidnightBSD's mport package manager before 2.7.8 trusts the TMPDIR environment variable when extracting package metafiles, so an attacker who can influence the environment of a privileged (root or setuid/setgid) mport invocation can redirect temporary metadata extraction into a location they control. Exploitation requires a local foothold on a MidnightBSD host, a privileged mport run that inherits the attacker-supplied environment, and success in the extraction timing window, which keeps this a low-to-moderate-risk local path-integrity issue rather than a remotely exploitable flaw; no public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis. The issue is fixed in mport 2.7.8 via upstream PR 123 (commit 3790fa4), which ignores unsafe TMPDIR values in privileged contexts and rejects empty TMPDIR.
Unauthenticated price tampering in the RestroPress WordPress plugin (versions before 3.4.6) lets any remote attacker alter the client-supplied add-on price when items are added to or updated in the cart, then place an order at an arbitrary - including zero - total. The flaw is a server-side validation failure affecting only sites that run RestroPress with online ordering/cart-and-checkout enabled and paid item add-ons configured; no credentials or user interaction are required and default configurations of the affected versions are exploitable. Impact is limited to integrity of pricing/billing (CVSS 5.3, C:N/I:L/A:N) rather than data disclosure or code execution, and no public exploit code or confirmed active exploitation has been identified at time of analysis.
Improper control of resource identifiers in Omega Solution HRM OS (versions up to 20260717) allows an authenticated low-privilege user to enumerate the permission mappings of arbitrary roles by manipulating the roleId parameter of the /role-permission/permission endpoint. The outcome is confidentiality-only: role and permission metadata can be read, but no data can be modified and no code can be executed, and the CVSS v4.0 base is only 2.1 (assessed CVSS v3.1 4.3, AV:N/AC:L/PR:L/UI:N/C:L/I:N/A:N). Publicly available exploit code exists (PoC referenced via VulDB and the linked GitHub issue), but there is no confirmed active exploitation (not in CISA KEV); the vendor was contacted early and did not respond, and no vendor-released patch has been identified at time of analysis.
Information disclosure in ScadaBR up to and including version 1.1 allows an attacker to pull the complete project export - data sources, data points and graphical views - by invoking the unprotected EmportDwr.createExportJSON DWR method through /ScadaBR/export_project.htm. The vendor's CVSS 4.0 vector lists PR:N, but the fix adds Common.getUser() plus Permissions.ensureAdmin(), which indicates the endpoint executes inside an authenticated session, so realistic exploitation requires a valid low-privilege ScadaBR account rather than true anonymous access; impact is confined to read-only configuration disclosure with no integrity or availability effect. Publicly available exploit code exists and the issue is fixed in ScadaBR 1.2.0, though there is no confirmation of active exploitation.
Information disclosure in nvm versions before 0.40.8 allows a local attacker who controls a repository to read arbitrary files readable by the invoking user when the developer runs `nvm use`, `nvm install`, or `nvm which` with a crafted `.nvmrc`, or when the user manually runs `nvm alias` with a traversing name. The path traversal in alias resolution causes nvm to print non-comment lines from the opened file in an error message; the automated `.nvmrc` route exposes only the first non-comment/non-empty line, while the manual `nvm alias` route can expose all such lines. No public exploit code or active exploitation has been identified at time of analysis, and the vendor addressed the issue in nvm 0.40.8.
Integer underflow in the PE parser of Manalyze 1.0.0 (PE::_parse_debug in manape/pe.cpp) can be triggered when the tool processes a crafted Portable Executable whose IMAGE_DEBUG_MISC debug-directory entry declares a Length smaller than the misc structure header, causing the computed string length to wrap to a very large unsigned value and the parser to read beyond the intended buffer. Exploitation is not remote in practice: it requires a local user (typically a malware analyst) to voluntarily run the unpatched Manalyze CLI against the malicious sample, so the assessed risk is low (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L), with impact largely confined to the parsing process - the tag 'Information Disclosure' reflects the out-of-bounds read potential rather than confirmed data exfiltration. No public exploit code and no active exploitation have been identified at time of analysis, and an upstream fix commit (3e299685759f4f767088871de58c5d07f98ee382) is available.
Information disclosure in D-Link DIR-X1860Z routers running firmware up to 1.0.2.220120.165402 lets unauthenticated users on the same local network segment read sensitive data through two ubus JSON-RPC handlers, routerd.wificfg_get and routerd.get_rand_key. The bug is reachable only from the adjacent network (LAN, guest WiFi, or a compromised local device) and carries low confidentiality impact with no integrity or availability effect, and no public exploit identified at time of analysis. D-Link ships a HOTFIX firmware (1.0.7.260821.161908) that resolves the issue, but the DIR-X1860Z is an end-of-life product, so exposure is concentrated on unpatched units still in service.
Hardcoded default secrets and credentials in aiyiyi121 SxDevOps 1.0/1.1 let unauthenticated remote attackers obtain sensitive information from instances that still run the shipped defaults - a Django SECRET_KEY of 'change-me' and the documented demo/admin password (for example Admin@123456) published in the project README. The issue is CWE-200 (exposure of sensitive information), rated CVSS 4.0 6.9 with confidentiality-only impact; no public exploit code has been identified at time of analysis, and any operator who set a strong SECRET_KEY, changed the admin/demo password, or disabled the demo accounts before exposing the service is not affected, so realistic risk is confined to negligently configured default installs of a niche self-hosted tool. The vendor was contacted early and issued a fix in commit 2b4bf8585c3e731e7a8af30801ea46680bc783f9.
Information disclosure in the Meow Gallery WordPress plugin before 5.5.5 lets authenticated users holding Author-level access or higher pull back metadata - titles, authors, dates and publish statuses - belonging to other users' draft and private posts. The vulnerable post-data retrieval routine performs neither a proper capability check nor owner-scoping of results, so a low-trust Author account on a multi-author site can enumerate unpublished content it was never meant to see; post bodies themselves are not exposed and there is no write, modify or denial-of-service impact. A publicly available exploit code exists, but the flaw is not confirmed actively exploited (no CISA KEV listing), and the risk is genuinely low-priority: it is not reachable by anonymous visitors, requires a valid Author-or-higher login (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N in our assessment), and matters mainly on sites where lower-trust Author accounts coexist with genuinely sensitive unpublished material.
Non-privileged applications running on a ZTE nubia Z80 Ultra (NX741J) smartphone can retrieve the device's Wi-Fi MAC address by querying the read-only factory_mac_address field exposed through the Android Settings.Secure content database, defeating the platform's normal restriction on hardware MAC address access. The issue is purely local (assessed CVSS:3.1/AV:L/AC:L/PR:N/UI:N, base score 3.3, C:L/I:N/A:N), requires an attacker-supplied app to already be installed and executing on the handset, and leaks only a single low-sensitivity hardware identifier whose main value is device tracking rather than data compromise. According to available intelligence, no public exploit has been identified at time of analysis and the CVE is not listed in CISA KEV; deployment is limited to a single consumer handset model, which keeps overall risk low.
Filter bypass in PHP-FTS (olivier-ls/php-fts) through version 1.1.3 allows an authenticated remote attacker to defeat document-scoping filters used by consuming applications for ownership or multi-tenant isolation, exposing search results the application intended to hide. The flaw resides in SearchEngine::matchesSingleFilter in src/SearchEngine.php, where filter values were compared with loose `==` and non-strict `in_array()`; because PHP treats any non-empty string as equal to boolean true, a filter value of true matched every document with a non-empty value in that field, and the string '42' matched the integer 42, enabling retrieval of other users' or tenants' records. Publicly available exploit code exists (a proof-of-concept write-up is referenced alongside the CVE from VulDB and a GitHub PoC repository), and the issue is not listed in CISA KEV, so no confirmed active exploitation is known; the risk is context-dependent and moderate, materializing only where the application relies on PHP-FTS filters as an access-control boundary and passes untyped request input directly into filter construction.
A use-after-free memory-safety flaw in Exim before 4.100.1 can crash the mail transfer agent process when the daemon is compiled against the GnuTLS TLS backend and configured with certain non-default TLS settings; once a vulnerable server is reachable over the network, no authentication (PR:N) or user interaction (UI:N) is required, but the CVSS vector reflects high attack complexity (AC:H) because the triggering configuration is unusual and non-default. The assessed impact is availability-only (C:N/I:N/A:L) - a crash or degraded service rather than code execution or data exposure. There is no confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis, so practical risk is confined to the narrow subset of Exim deployments using GnuTLS with the specific triggering TLS options.
Credential exposure in OpenPanel's Model Context Protocol (MCP) integration causes MCP authentication tokens supplied as URL query parameters to be written verbatim into plaintext application logs, letting anyone who can read application stdout, container/pod logs, or a centralized logging/SIEM store harvest base64-encoded credentials and replay MCP requests for read access to project analytics. The issue is gated by prior read access to the log data (CVSS 4.0 vector AV:L/PR:L; the independent assessment scores it low at CVSS 3.1 with only low confidentiality impact and no integrity or availability effect), so it is a real but low-priority defect rather than a remote unauthenticated path. No public exploit identified at time of analysis, and no confirmed actively exploited (CISA KEV) status is indicated in the provided data.
Unauthenticated information disclosure in the WordLift - AI powered SEO - Schema plugin for WordPress affects all versions up to and including 3.54.10, allowing remote attackers with no credentials to harvest the title, body content, author, publication and modification dates, word count, comment count, and other metadata of private, draft, and pending posts. The flaw stems from the plugin's /wordlift/v1/jsonld/ REST routes being registered with a permission_callback of '__return_true', combined with a downstream JSON-LD converter that calls get_post() without validating post status or the caller's capabilities, so sequential post-ID enumeration bypasses WordPress core access controls. No public exploit code was identified at time of analysis and the vulnerability is not reported as actively exploited; the CVSS 3.1 base score of 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) reflects a confidentiality-only, low-complexity disclosure with no integrity or availability impact.
Any authenticated WordPress user holding contributor-level capabilities or higher can pull the entire customer dataset out of the Easy Appointments plugin (all versions up to and including 3.12.27) because the handle_customers_ajax handler returns ea_customers records without enforcing an adequate capability check. The exposed records contain personally identifiable information such as names, email addresses, mobile numbers, dates of birth, and physical addresses, so the impact is a high-confidentiality, read-only disclosure with no integrity or availability effect, consistent with the assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N score of 6.5 (MEDIUM). Exploitation is not possible for unauthenticated visitors - an attacker must first hold a low-privilege account - and no public exploit identified at time of analysis; risk is concentrated on multi-author sites, membership sites, or any installation that hands out contributor accounts or has self-registration mapped to elevated default roles.
Unauthenticated information disclosure in the Bread WordPress plugin (versions up to and including 2.9.12) lets any remote visitor read the plugin's entire configuration export, including the PDF protection password stored in plaintext, by simply requesting the /?export-meeting-list=1 endpoint. The flaw is trivially reachable: the download_settings function is registered on the plugins_loaded hook and explicitly permits execution on non-admin public pages, so no authentication, authorization, or user interaction is required (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U, base 5.3 MEDIUM). Impact is bounded to disclosure of the stored protection_password rather than site credentials or code execution, and no public exploit code has been identified at time of analysis; the practical risk depends on how sensitive the protected PDF meeting lists and their shared password are in a given deployment.
Missing authorization in the Nimble Page Builder WordPress plugin through 3.3.8 lets an authenticated user with only Subscriber-level access read the page-builder content of arbitrary non-public posts and pages, including drafts, pending, private and scheduled items. The plugin's authenticated AJAX action returns stored page-builder content without verifying that the requester is allowed to edit the target post, so an attacker can enumerate post IDs and exfiltrate unpublished content; publicly available exploit code exists and the WPScan disclosure serves as the entry point, though the issue has not been reported as actively exploited in CISA KEV. Impact is confined to information disclosure (CVSS 3.1 4.3, C:L only, PR:L, no integrity or availability effect), and sites that allow open user registration effectively lower the bar to any remote registrant.
Unauthenticated attackers can impersonate the Better Messages plugin's own internal AI bot accounts on WordPress sites running versions up to and including 2.15.33, gaining entry to administrator-restricted chat rooms and reading the private message history of other users. The flaw is entirely pre-authentication (CVSS vector PR:N/UI:N) and requires only that unauthenticated guest registration is enabled and that the server forwards the client-supplied X-Real-IP header to the plugin, which stores it verbatim; the plugin's is_ai_bot_user() check then prefix-matches the attacker-chosen value against 'ai-chat-bot-'. No public exploit code was identified at time of analysis and there is no CISA KEV confirmation of active exploitation, but the low complexity and lack of any credential requirement make the issue straightforward to abuse where restricted rooms exist. The vendor-assigned score is 5.3 (Medium, C:L/I:N); our reassessment raises confidentiality to High and adds a Low integrity impact because the same bypass allows posting into restricted rooms, netting a materially higher severity than the published vector implies.
Sensitive information disclosure in the Divi Essential WordPress plugin through version 5.8.1 allows any authenticated user holding Subscriber-level access or above to enumerate every table in the site's WordPress database and read a caller-controlled number of rows from each, exposing usernames, emails, hashed passwords, session tokens, secret keys, and plugin-stored API credentials. The flaw is trivially reachable because the dnxte_get_database_tables and dnxte_get_database_data AJAX handlers only perform a nonce check when the 'nonce' POST parameter is supplied - omitting it skips the check entirely - and no current_user_can() capability enforcement exists. Authentication requirements are confirmed as low-privileged (CVSS PR:L) rather than unauthenticated, so the practical attack surface depends on whether the site allows open user self-registration; no public exploit code was identified at time of analysis, and the impact is confidentiality-only with no modification of data or loss of availability.
Local file disclosure in Calculator Lock for Android allows a local actor with shared external storage access, such as an authorized non-root ADB shell or a co-resident file-reading app, to copy the vault's SQLite database and media files without entering the calculator passcode. The published CVSS is 6.8, and the independent assessment (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) confirms high confidentiality impact with no integrity or availability impact; the passcode still gates the in-app UI. The independent assessment classifies this as a genuine but low-urgency local issue, and no public exploit identified at time of analysis.
SIP body-length truncation in Suricata 8.0.0 through 8.0.5 causes the IDS/IPS engine to expose only the first 65,536 bytes of oversized SIP request or response bodies to frame-based inspection, letting an unauthenticated remote attacker hide malicious content in the omitted remainder and evade detection. The flaw resides in the Rust SIP parser, which stores body offsets and lengths in 16-bit fields, so any body larger than 65,536 bytes wraps the stored length; this only matters on deployments that enable SIP application-layer parsing and run rules referencing frame:request.body or frame:response.body, and it degrades detection integrity only (no crash, no code execution, no data exposure). Per the CVSS vector (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N, score 3.7) the impact is limited to integrity of the detection pipeline, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Unauthenticated information disclosure in CordysCRM (1Panel-dev) versions prior to 1.7.2 lets any network-reachable caller retrieve CRM form metadata via GET /mcp/form/config/{formKey}, exposing field names, types, required flags, default values, options, validation rules, and binding sources. The flaw exists because ShiroFilter marks the /mcp/** path as anonymous and McpController.getMcpField carries no permission annotation, so the endpoint is reachable without credentials (CVSS 4.0 base 6.9; independent assessment CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N). Impact is limited to schema/metadata disclosure rather than direct access to customer records, and no public exploit code has been identified at time of analysis; exploitation does require knowledge or brute-forcing of valid formKey identifiers.
A local time-of-check/time-of-use (TOCTOU) race condition in cockpit-files on Red Hat Enterprise Linux 9 and 10 allows an unprivileged local attacker to redirect a privileged chown operation to an arbitrary file by replacing a newly created directory with a symlink, resulting in potential information disclosure or unauthorized modification of sensitive files. Exploitation requires a privileged operator to trigger directory creation with owner assignment via cockpit-files inside an attacker-controlled writable parent directory, and the attacker must win a narrow timing window (CVSS 3.1: AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N, 6.0). No public exploit code or confirmed active exploitation was identified at time of analysis; this is a modest-priority local privilege/integrity issue rather than a mass-exploitation threat.
HTTP request smuggling in IBM WebSphere Application Server and WebSphere Application Server Liberty - as bundled in IBM CICS TX Advanced per the affected CPE - lets remote attackers desynchronize request framing between a front-end intermediary and the WebSphere back end, enabling request tampering or response poisoning. Exploitation requires the server to sit behind a reverse proxy, load balancer, or CDN that parses Content-Length/Transfer-Encoding framing differently than the back end; no authentication or user interaction is needed (PR:N/UI:N), but attack complexity is high (AC:H) because the attacker must find and reliably trigger a specific parser discrepancy in the real deployed chain, and a directly exposed server with no divergent front-end parser is not smuggle-able. Impact is bounded to low confidentiality and integrity with no availability effect (CVSS 3.1 base 4.8); this is a genuine but modest-severity issue rather than a top priority, and no public exploit was identified at time of analysis.
HTTP request smuggling in IBM WebSphere Application Server 8.5 can allow unauthenticated remote attackers to desynchronize request processing when the server sits behind or in front of an HTTP intermediary with mismatched Content-Length parsing, potentially leading to credential theft, cache poisoning, or request hijacking. The flaw (CWE-444) rates 6.5 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N) and requires a specific proxy-layer mismatch and concurrent traffic; no public exploit identified at time of analysis. Vendor patch is available and the risk is assessed as moderate and non-urgent.
HTTP request smuggling in IBM WebSphere Application Server Liberty - the runtime bundled with IBM CICS TX Advanced 10.1 - lets remote, unauthenticated attackers desynchronize HTTP message framing between an upstream HTTP parser and the Liberty backend, so a smuggled request can be processed as if it came from the trusted front-end, with low confidentiality and integrity impact on subsequent requests sharing the connection. Exploitation requires a multi-tier topology (reverse proxy, load balancer, or CDN in front of or behind Liberty) where the two parsers disagree on Content-Length/Transfer-Encoding or chunked framing, and is rated high complexity because the specific parsing gap must be discovered and precisely crafted while connection reuse must be achievable; no user interaction is required. Risk is moderate and consistent with the vendor CVSS of 4.8 (Medium); no public exploit identified at time of analysis, and patch is available from the vendor.
In libsmpp35 from 0.1.0 through 1.8.0 out of bound read issue was found in the at smpp34_unpack() function via attacker controlled SMPP PDUs, leading to memory corruption.
Local information disclosure in cockpit-machines on Red Hat Enterprise Linux 9 and 10 allows an authenticated local user to read plaintext VM credentials - including passwords - that the component passes directly on process command-line arguments during VM creation or installation. Exploitation is timing-dependent: the secret is only readable while a provisioning operation is in flight, and it also requires that /proc process arguments remain visible to other users (i.e., the host is not hardened with a hidepid-style mount option), so risk concentrates on multi-user or shared virtualization hosts. It yields no code execution and no privilege escalation, but a disclosed password compromises access to the affected VM; no public exploit code has been identified at time of analysis and the flaw is not confirmed actively exploited (not in CISA KEV).
Local information disclosure in cockpit-machines on Red Hat Enterprise Linux 9 and 10 allows an authenticated local attacker who can enumerate other users' process arguments to read guest VM installation credentials such as rootPassword and userPassword. The credentials are passed by install_machine.py as a JSON command-line argument during VM creation, so exposure is limited to the window while an administrator's installation workflow is running and depends on the host's process-visibility policy (e.g. /proc without hidepid=2). Publicly available exploit code exists, but there is no confirmed active exploitation; the issue requires local access plus a concurrently active install and cannot be triggered remotely or unauthenticated.
Local information disclosure in the cockpit-machines package on Red Hat Enterprise Linux 9 and Red Hat Enterprise Linux 10 lets an unprivileged local user capture a Red Hat Subscription Management (RHSM) offline token that is passed as a command-line argument to a helper script during token validation. Rated 5.0 (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N), the impact is confidentiality-only: a local account that can read other processes' metadata (for example /proc/<pid>/cmdline via ps) must catch the brief window in which a privileged operator runs the validation, and the stolen token can then be exchanged for RHSM access tokens. There is no public exploit code identified at time of analysis and no CISA KEV entry; Red Hat tracks the issue as CVE-2026-92745 (EUVD-2026-83260).
Session fixation in the password-protected shared-notes flow of SysReptor (Syslifters) before version 2026.68 lets an attacker who can plant a known, unauthenticated share-page session cookie in a victim's browser reuse that session after the victim enters the correct note password, gaining access to that shared note. The main SysReptor login is unaffected; only the 'publicshareinfo-auth' / 'sharednote-detail' share flow fails to rotate the session identifier on successful authentication (CWE-384). Exploitation requires a separate cookie-injection capability (for example an XSS vector, a shared or attacker-controlled device, or a network man-in-the-middle position) plus precise knowledge of the shared-note URL the victim will authenticate against, and the victim must actively submit the password, so the assessed CVSS 3.1 score is 3.7 (AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N); no public exploit code was identified at time of analysis.
Unauthenticated holders of a SysReptor public note share link can retrieve project-wide collaborative-editing metadata for any deployment running a version prior to 2026.55, because the public-share WebSocket consumer joins the same collaboration group as authenticated project members and forwards client-information, connect/disconnect, awareness, and deletion events without restricting them to the shared note subtree. This leaks project member usernames and display names plus the identifiers and live editing activity of notes that were never shared; note content itself stays protected and no write access is granted. Our reassessment rates the issue CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N (5.3), higher than the vendor-assigned 3.5 (PR:L/UI:R) because the metadata is returned to an unauthenticated share-link holder on connection, though exploitation still requires possession of a valid share link. There is no public exploit code and no confirmed active exploitation (CISA SSVC exploitation: none); the fix is included in release 2026.55 via commit 1e52e5058b0c7f420dc45c87ad72e7a4585477b1.
AnyCable (anycable-go) through 1.6.14 ships its telemetry subsystem enabled by default with a hardcoded public auth token ('secret' in telemetry/config.go) and derives its cluster fingerprint by hashing the full configuration file plus raw os.Args, which can include values passed via --secret, --jwt_secret, and --http_rpc_secret; an adversary who can MITM or DNS-hijack telemetry.anycable.io can intercept the outbound telemetry POST, and because the client's token is publicly known it offers no protection. The transmitted clusterFingerprint is a SHA256 digest rather than raw plaintext, so meaningful secret recovery additionally depends on low-entropy secrets, and the required network-interception position makes this a moderate-to-low real-world risk best characterized as a hardcoded-credential and telemetry-exposure design flaw rather than a directly exploitable credential leak. Exploitation status: no public exploit code identified at time of analysis and no confirmed active exploitation (CISA KEV); the GHSA advisory documents only a conceptual DNS-spoofing reproduction. Vendor-released patch: 1.6.15.
Unauthenticated remote attackers can query the SNMP v2c service on Grandstream GWN7660ELR access points running firmware before 1.0.27.6 when the service is left with the factory-default community string 'public', harvesting system metadata such as OS and kernel versions, process names and command-line arguments, interface configuration, routing and ARP tables, active TCP connections, and filesystem paths. The CVSS 4.0 base score is 6.9 (vector CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N) and our independent assessment maps it to CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N - a read-only reconnaissance issue requiring only UDP/161 reachability, with no write, code execution, or lateral-movement primitive on its own. No public exploit code has been identified at time of analysis and the CVE is not in CISA KEV, so this is a genuine but modest-priority information-disclosure weakness whose real-world exposure depends on whether SNMP is enabled, still using the default community string, and reachable from untrusted networks; it is fixed in firmware 1.0.27.6.
File-system information disclosure in IBM WebSphere Application Server 9.0 and 8.5 lets an attacker positioned on an adjacent network segment query the FileTransfer servlet and learn details about the server's file system, such as file and directory names or paths. Per the vendor-supplied vector (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, base 4.3), the flaw is rated unauthenticated and requires no user interaction, but the adjacent-network precondition means the attacker must already sit on the same management/admin LAN or WebSphere Network Deployment segment rather than reaching the service from the open Internet, and impact is limited to low-confidentiality disclosure with no integrity or availability effect. No public exploit code has been identified at time of analysis, and the CVE is not listed in CISA KEV; overall this is a low-priority issue, though it is notable because WebSphere is widely deployed in large enterprises.
Cross-site request forgery token recovery in the Mojolicious Perl web framework (all versions prior to 9.48, tracked as cpe:2.3:a:mojolicious:mojo) lets an unauthenticated attacker recover a victim's per-session CSRF token through a BREACH compression side channel and then forge cross-site requests that pass csrf_protect. The attack only works in deployments that enable HTTP response compression and render the token into HTML (via csrf_field, csrf_token, or csrf_protect) while reflecting attacker-influenced content in that same compressed response; API-only deployments that never emit the token in HTML are explicitly unaffected. It is a high-effort, victim-interaction-dependent attack (CVSS 4.2, AC:H/UI:R) with no public exploit identified at time of analysis, and the vendor has shipped a fix in version 9.48 that masks the token with fresh randomness on every request.
HTTP request smuggling (CWE-444) in IBM WebSphere Application Server 8.5, 9.0, and Liberty lets an authenticated, low-privileged remote attacker desynchronize HTTP request framing between WebSphere and an intermediary so that one user's request boundaries are misattributed on a shared connection. The issue only manifests when WebSphere sits behind or in front of a second HTTP parser (reverse proxy, load balancer, or CDN) that disagrees with WebSphere on Content-Length versus Transfer-Encoding chunked handling; a standalone WebSphere instance with no fronting or backend HTTP hop is not affected, and the 4.2 score reflects high attack complexity, partial confidentiality and integrity impact, and no availability or scope change. No public exploit code and no confirmed active exploitation were identified at time of analysis, and a vendor patch is available per IBM's advisory.
Heap out-of-bounds read in libheif prior to 1.23.2 lets an application that builds inline-mask region metadata through the library's writer API leak adjacent heap memory or crash. Specifically, heif_region_item_add_region_inline_mask_data() stored a caller-supplied mask buffer without verifying that mask_data_len equals ceil(width*height/8); a later heif_region_get_mask_image() render derives the number of bytes to read from the region geometry, so an undersized buffer causes the reader to copy bytes past the end of the allocation into the returned monochrome mask image. The file-parsing/decode path validates the canonical mask size and is explicitly not vulnerable, so merely opening a crafted HEIF/AVIF file does not trigger the bug; exploitation requires a local program in which attacker-influenced geometry and mask data disagree, consistent with the assessed vector AV:L/AC:H/PR:N/UI:N (CVSS 4.0). There is no confirmed active exploitation (no CISA KEV listing), and no public exploit code was identified at time of analysis; the issue is a genuine but low-priority memory-safety defect rather than an emergency, and version 1.23.2 fixes it.
Sensitive information exposure in IBM Common Licensing Agent 9.0 through 9.0.0.2 and IBM Administration and Reporting Tool (ART) 9.0 through 9.0.0.2 allows an authenticated low-privilege user to cause error messages to reveal environment, user, or associated data details. The assessed vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N (CVSS 4.3), so exploitation requires valid authentication, has low complexity, and yields only reconnaissance-grade confidentiality impact with no integrity or availability impact. No public exploit was identified at time of analysis, and this is a low-priority information-disclosure issue rather than an actively exploited flaw.
Denial of service in OpenImageIO versions prior to 3.0.21.0, 3.1.16.0, and 3.2.0.3-beta1 occurs when the library processes a truncated TGA file while writing GIF output, triggering a signed 32-bit integer overflow in GifSplitPalette() that leads to an out-of-bounds read (CWE-125) and a process crash. The CVSS v3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H) indicates the attacker is unauthenticated (PR:N) but requires local access and user interaction, with no remote or unauthenticated network trigger. No public exploit code or active exploitation has been identified; this is a low-priority hardening issue for workflows that transcode untrusted images to GIF.
IBM Controller versions 11.0.0 through 11.0.1 FP7 and 11.1.0 through 11.1.3 FP1 send sensitive data in cleartext, allowing an attacker who occupies a man-in-the-middle position on the network path to capture confidential information. Exploitation requires an on-path adversary (e.g., via ARP or DNS spoofing or a compromised intermediary) but no authentication or user interaction; the CVSS 3.1 base score is 5.9 with high confidentiality impact but no integrity or availability impact. No public exploit code or confirmed active exploitation has been identified, and IBM has released a patch.
IBM Cognos Analytics versions 12.0.4 through 12.0.4 FP2 and 12.1.0 through 12.1.3 FP1 embed sensitive information within source code delivered to clients, allowing an authenticated user with access to that code to harvest data that can be used to mount further attacks against the system. The flaw carries a CVSS base score of 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) and requires a valid Cognos Analytics account, so exploitation is gated behind existing credentials or a foothold rather than being openly reachable; impact is limited to low confidentiality loss with no integrity or availability effect. No public exploit code has been identified at time of analysis, and the issue has not been confirmed actively exploited (CISA KEV); vendor-released remediation is available, making this a low-priority hardening item rather than an urgent threat.
Information disclosure in IBM Cognos Analytics 12.1.0 through 12.1.3 FP1 and 12.0.4 through 12.0.4 FP2 allows an unauthenticated attacker on a shared network segment to capture sensitive data because the product uses insecure network communication (CWE-327). Exploitation requires the attacker to achieve a man-in-the-middle or traffic-capture position on the same network, making it impractical over the open internet; the impact is limited to confidentiality. The vendor CVSS score of 5.9 is a fair reflection of the moderate risk, no public exploit code has been identified, and a vendor patch is available.
IBM QRadar deployments running 7.5.0 through 7.5.0 UP15 Interim Fix 006 expose sensitive backup-file contents to any holder of a valid QRadar account, because those backup files are stored with incorrect permissions. Exploitation requires authentication (CVSS vector PR:L) but no administrative rights and no user interaction, and an attacker who satisfies that bar can read configuration, credential, or event data captured in the affected backups, yielding a high confidentiality impact (C:H) with no integrity or availability effect. This is a moderate-priority information-disclosure issue rather than a high-urgency emergency: no public exploit code has been identified at time of analysis, the flaw is not in CISA KEV, and the authentication prerequisite plus the need for an unpatched interim-fix level are the principal limiting factors.
Heap out-of-bounds read in OpenImageIO's IFF image reader (src/iff.imageio/iffinput.cpp, IffInput::readimg()) affects all releases prior to 3.0.20.0, 3.1.15.0, and 3.2.0.3-beta1, allowing a caller that opens a crafted uncompressed 16-bit IFF file containing a z-buffer channel to trigger a crash or leak adjacent heap contents into the decoded image output. The flaw is an allocation/stride mismatch: the temporary scanline buffer is sized from m_header.rgba_count while the subsequent memcpy uses m_header.pixel_bytes(), whose stride also counts z-buffer bytes, producing an oversized copy. Exploitation requires local, user-initiated parsing of the malicious file (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H, 6.1) with no privileges needed but no remote zero-interaction path; no public exploit code and no confirmed active exploitation were identified at time of analysis, and EPSS/KEV data were not provided. Vendor-released patches exist in versions 3.0.20.0, 3.1.15.0, and 3.2.0.3-beta1.
Unauthenticated information disclosure affects the Multicluster Observability Addon in Red Hat Advanced Cluster Management for Kubernetes, enabling attackers on the adjacent network to access a debug endpoint that leaks goroutine, heap, and command-line profiling data. The misconfiguration originates in the underlying addon-framework library, which exposes the endpoint without requiring credentials; exploitation only requires a basic encrypted (TLS) connection. No public exploit has been identified at time of analysis, and the vulnerability does not permit remote code execution, but the exposed profiling information could aid reconnaissance or further attacks.
IBM Controller releases 11.0.0 through 11.0.1 FP7 and 11.1.0 through 11.1.3 FP1 can return detailed technical error messages to the browser, allowing remote, unauthenticated attackers to harvest implementation details about the affected system (CWE-209). Per the CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, exploitation is network-reachable and requires no credentials or user interaction, but the impact is confined to low-value information disclosure that is most useful as reconnaissance for follow-on attacks rather than for direct compromise. No public exploit code has been identified and the issue is not listed in CISA KEV, so this is a genuine but low-priority weakness whose practical risk largely depends on whether the Controller web interface is reachable from untrusted networks.
An out-of-bounds read in the Zephyr RTOS gPTP (IEEE 802.1AS) Ethernet layer lets an attacker on the same link crash-free but silently expose memory contents: a truncated Ethernet frame with ethertype 0x88F7 and fewer than 34 bytes of payload is accepted by gptp_handle_msg(), which dereferences a gPTP header pointer that extends past the received data and then retains the short packet for later state-machine parsing. Affected are Zephyr releases from 1.13.0 up to (but not including) 4.4.2 built with CONFIG_NET_GPTP on an interface configured as a gPTP port; no authentication or user interaction is required (PR:N/UI:N), though exploitation is limited by the adjacent-only vector and the requirement for a link that can deliver sub-minimum frames (for example the native_sim TAP driver or a MAC that accepts undersized frames). The impact is read-only and low (CVSS 3.1 base 3.1, C:L/I:N/A:N): under the default fixed-size buffer allocator only stale recycled buffer contents within the 128-byte fragment are disclosed, while a genuine out-of-bounds read requires the experimental CONFIG_NET_BUF_VARIABLE_DATA_SIZE allocator. No public exploit code was identified at time of analysis and the issue is not listed in CISA KEV; an upstream fix commit and vendor advisory are available.
HTTP request smuggling in Netty's HTTP/1.1 decoder (HttpObjectDecoder and the HttpRequestDecoder built on it) lets remote, unauthenticated attackers send a chunk-size line containing an embedded bare carriage return - for example `0\rX` - because strict chunk-line validation is skipped whenever the size line carries no `;` chunk extension, causing a request-boundary desync when Netty shares a connection with a second HTTP intermediary that frames the message differently. The flaw reaches every application and Red Hat product that embeds Netty, including AMQ Broker 7, AMQ Clients, Quarkus, Camel 4 for Quarkus 3, Camel for Spring Boot 4, Keycloak / Red Hat Single Sign-On, JBoss EAP 7 and 8, Fuse 7, Data Grid 8, Apicurio Registry 3 and Debezium 3, while independent assessment keeps it at CVSS 6.5 with AC:H because a standalone Netty service with no disagreeing proxy in the chain yields little practical smuggling impact. The public report includes a reproducible PoC test harness, but there is no CISA KEV listing and no evidence of active exploitation.
Imager versions before 1.036 for Perl disclose uninitialised heap memory reading a paletted image with pixel indexes past its colour map in i_gpix_p and i_glin_p. The palette is allocated uninitialised, and only the entries a reader adds count as populated. The TGA reader stores pixel indexes without checking them against the colour map. i_gpix_p() rejects only an index greater than the count, so an index equal to it reads the first unpopulated entry, and getpixel() returns it. i_glin_p() skips any index at or beyond the count without writing that pixel to the caller's buffer. The palette-to-RGB conversion reads each row through an uninitialised buffer, so those pixels of the converted image hold prior heap contents. Reading an attacker-supplied image through Imager->read() and then fetching its pixels or converting it to RGB discloses process heap memory.
Policy evasion in Zscaler Internet Access File Type Control can allow a file to be improperly evaluated or attributed, potentially bypassing file-type enforcement in rare circumstances. The issue affects organizations using ZIA with File Type Control actively enforcing policies and requires a malicious file transfer through the ZIA tenant, low privileges (PR:L), and user interaction (UI:R). Impact is limited to low confidentiality/integrity policy-control evasion with no availability impact or code execution; no public exploit identified at time of analysis, and vendor-managed remediation is applied centrally by Zscaler.
Name-constraint bypass in rustls-webpki versions 0.101.0 through 0.103.11 and 0.104.0-alpha.1 through 0.104.0-alpha.5 allows a misissued wildcard certificate to escape permitted-subtree DNS name constraints, potentially permitting names outside the intended subtree. The flaw is reachable only after signature verification succeeds and requires a misissued wildcard certificate from a name-constrained CA, making real-world exploitation narrow and high-complexity (assessed CVSS 3.1 base 2.1, PR:N, AC:H). No public exploit identified at time of analysis; vendor-released patches are available in 0.103.12 and 0.104.0-alpha.6.
rustls-webpki 0.101.0 through 0.103.11 and 0.104.0-alpha releases before 0.104.0-alpha.6 accept X.509 name constraints that apply to URI names instead of enforcing them, so a misissued certificate that violates such a constraint is treated as valid. Impact is deliberately narrow: URI name constraints are only reachable after successful signature verification, the library provides no API for asserting URI names, and exploitation therefore requires a certificate authority in the trusted path to have misissued a certificate. There is no public exploit identified at time of analysis, no CISA KEV listing, and our assessment treats this as a low-priority, defense-in-depth hardening fix consistent with the vendor's CVSS 4.0 score of 2.1 rather than an urgent vulnerability.
Arbitrary file read in NetBackup Flex OS (versions before 6.4) lets an authenticated user who can reach the appliance's management shell read files outside the intended scope - including sensitive system configuration and credential material - by supplying a specially crafted path argument to a diagnostic command. The issue carries a CVSS 4.0 base score of 4.8 and is classified as CWE-347 (improper verification of cryptographic signature), with the advisory's associated tags pointing to an information-disclosure / JWT-style attack path. Exploitation requires valid management-shell credentials and local access to the appliance, so it is not reachable over the network without an existing account; no public exploit code has been identified at time of analysis, the CVE is not listed in CISA KEV, and vendor patches are available.
A signed/unsigned type mismatch in Netty's Memcache binary protocol codec desynchronizes frame boundaries, allowing an unauthenticated, network-positioned attacker to smuggle responses across a shared or proxied memcache connection (CVSS 3.1 base 6.5, Medium). The flaw is reachable only when the Memcache binary codec is explicitly wired into a network-exposed Netty pipeline - a non-default configuration - and the affected code ships inside Red Hat Fuse 7, JBoss Enterprise Application Platform 7, Single Sign-On 7, and the Red Hat Build of Apache Camel for Spring Boot 4. No public exploit code has been identified at time of analysis, and there is no confirmation of active exploitation (not in CISA KEV); impact is limited to confidentiality and integrity (C:L/I:L) with no availability effect.
Information disclosure in Synology DiskStation Manager (DSM) lets unauthenticated remote attackers read a limited set of files by overwhelming the built-in Auto Block brute-force protection with sustained authentication attempts. The root cause is an improper restriction of excessive authentication attempts (CWE-307), and exploitation is technically difficult (CVSS 3.7, AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N) with the payoff confined to low-confidentiality reads and no write or denial-of-service capability. Affected versions are DSM before 7.2.1-69057-10, 7.2.2-72806-7, and 7.3.2-86009-2; no public exploit identified at time of analysis, and this remains a low-priority finding despite being remotely reachable and unauthenticated.
Unauthenticated remote attackers can query the Desktop API in Synology DiskStation Manager (DSM) to retrieve non-sensitive information, affecting DSM versions before 7.2.1-69057-10, 7.2.2-72806-7, and 7.3.2-86009-2. The CVSS 3.1 score is 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N), and while no public exploit code or active exploitation has been identified at time of analysis, the flaw still offers reconnaissance value because no authentication or user interaction is required. Given the limited confidentiality impact and lack of integrity or availability effects, this is a low-priority issue, with risk primarily determined by whether the DSM management interface is internet-facing.
Information disclosure in Synology DiskStation Manager (DSM) allows remote authenticated users to obtain sensitive information by directly requesting the Wallpaper Path resource, bypassing intended navigation controls. Affected versions are DSM before 7.2.1-69057-10, 7.2.2-72806-7, and 7.3.2-86009-2. Exploitation requires a valid DSM account (PR:L) and network access to the DSM web interface; no public exploit identified at time of analysis. Vendor patches are available in the listed fixed builds.
HCL BigFix Service Management exposes internal IP addresses through its own HTTP responses - response headers, error messages, or rendered page content - allowing anyone able to reach the instance to harvest RFC1918 addressing and infer the internal network topology behind it. The consequence is reconnaissance only: no data modification, no service disruption, and a low vendor base score of 3.1, making this a low-priority item rather than an urgent one. No public exploit code was identified at time of analysis and there is no KEV or EPSS signal in the supplied data. The vendor vector specifies PR:L (a valid session) while the description claims an unauthenticated attacker, so authentication requirements are not confirmed from available data; the vendor's AC:H also implies an additional non-trivial condition or timing is needed to elicit the leak.
Improper encoding and escaping of output in the Auth API of Synology DiskStation Manager (DSM) lets remote, unauthenticated attackers retrieve information the vendor classifies as non-sensitive, affecting deployments before 7.2.1-69057-12, 7.2.2-72806-9, 7.3.2-86009-4, and 7.4-90075. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, 5.3) confirms exploitation needs no credentials, no user interaction, and no non-default configuration, so the only meaningful barrier is impact rather than access. There is no public exploit identified at time of analysis and no KEV listing, and because disclosure is limited to non-sensitive information, the practical value to an attacker is reconnaissance and fingerprinting rather than direct compromise; vendor-released patches exist in the fixed DSM builds published under Synology advisory SA_26_13.
Plaintext third-party AI provider API keys can be extracted from any WordPress site running the GPTranslate - Multilingual AI Translation Agent plugin at version 2.34.6 or earlier, because the plugin emits the stored credential into a public front-end JavaScript asset loaded by enqueue_frontend_scripts. The exposure is unauthenticated and requires no user interaction - an attacker only needs to fetch any public page and apply the inverse transformation that is itself bundled in the plugin's own public JavaScript to recover the key in cleartext (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, 5.3 Medium as published; our assessment raises the confidentiality component to High given that a raw billing-capable credential is disclosed, yielding 7.5). Keys for OpenAI, DeepL, xAI/Grok, Gemini, Claude, and Google Cloud Translation are all affected, and the default configuration (gpt-3.5-turbo in client mode) is vulnerable; only deepseek-* models and gpt-* models running in server-proxy mode correctly suppress key emission. No public exploit code was identified at time of analysis and the vulnerability is not listed in CISA KEV, though the recovery technique is trivially derivable from the plugin's own shipped assets, so treat exploitation as plausible and rotate credentials.
Unauthenticated visitors can strip the login- and URL-hiding protection from WordPress sites running the Hide My WP Ghost plugin before 7.0.11 by triggering the plugin's own loopback security-check request with a missing or incorrect verification value, causing the concealment to fail open and re-exposing the hidden WordPress login page location. The flaw is network-reachable, low complexity, and requires no authentication or user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, base 5.3), but its impact is deliberately narrow: it only reverts the site to its ordinary, unhidden login posture and does not bypass WordPress authentication, so real-world risk depends on the strength of the underlying credentials and any additional login protections in place. Publicly available exploit code exists and the issue is tracked by WPScan as well as ENISA EUVD-2026-82686; a vendor fix is available in version 7.0.11, and there is no indication of confirmed active exploitation (no CISA KEV listing) and no EPSS score was provided in the source data.
Unauthenticated attackers can strip the hardening protections from the Hide My WP Ghost WordPress plugin (versions before 7.0.11) by supplying a single WooCommerce-looking request parameter, which the plugin accepts as proof of a legitimate WooCommerce request and uses to switch off its firewall, threat detection and login/URL-hiding logic - re-exposing the concealed login and admin URLs on any request. The issue affects default installations where the plugin's protection features are enabled (its core purpose), requires no authentication, user interaction or non-default configuration (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, 5.3), and publicly available exploit code exists, with no confirmed active exploitation reported. The impact is indirect - WordPress core authentication is not bypassed - but any site treating this plugin as a meaningful obscurity control effectively loses that protection until it is upgraded to 7.0.11 or later.
Web cache poisoning in the Breeze Cache WordPress plugin before 2.5.15 allows unauthenticated remote attackers to append tracking-related query parameters that the plugin still caches responses for but omits from the page-cache key, causing a page rendered in the attacker's own request context to be stored under the clean URL's cache entry and served to every subsequent visitor. Exploitation requires only that page caching be active in its default configuration - no authentication, no user interaction, and no special setup (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N, 6.5) - and publicly available exploit code exists; the issue is not confirmed as actively exploited (not in CISA KEV). Impact is bounded to low confidentiality and integrity effects, exposing one visitor's rendered context to others and altering cached page content until the entry expires or is purged.
Missing authorization on an appointment-retrieval action in the Bookit - Booking & Appointment Calendar WordPress plugin before 2.6.0.5 lets an authenticated user holding a low-privilege Bookit-specific role pull other customers' appointment records, including names, email addresses, phone numbers and private booking comments. The underlying issue is a CWE-200 information-exposure pattern: the action returns booking PII without verifying that the caller owns the appointment or holds the capability that normally gates such data. Publicly available exploit code exists and WPScan published the finding, but there is no indication of active exploitation, impact is confined to confidentiality with no write or availability effect, and a vendor fix is available in 2.6.0.5 - making this a low-to-moderate priority disclosure issue rather than a high-severity threat.
King Addons for Elementor versions before 51.1.81 fail to enforce capability, post-status, or password checks when rendering the content of a requested post, allowing any authenticated user with Contributor-level access or higher to read the contents of private, draft, pending, and password-protected posts they are not authorized to view. The flaw is an authenticated information-disclosure issue (CWE-200) that requires only an active contributor-level account on a site running the affected plugin plus the choice of a target post ID; it grants no write, modification, or destructive capability. Publicly available exploit code exists, but there is no indication of confirmed active exploitation and the vendor has shipped a fix in 51.1.81; our independent assessment rates this a genuinely low-priority, though real and patch-worthy, authorization flaw (assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N).
An out-of-bounds read in GPAC's RTP depacketizer lets unauthenticated remote attackers crash or partially disclose memory by delivering a crafted 3GPP timed-text (TTXT) RTP payload with an oversized advertised length. The flaw lives in gf_rtp_parse_ttxt() in src/ietf/rtp_depacketizer.c and affects GPAC 26.08-DEV and earlier builds prior to abi-16.26; exploitation requires the target to be acting as an RTP receiver/depacketizer rather than simply parsing a local file. No public exploit code was identified at time of analysis and there is no confirmed active exploitation (CISA KEV), so this is a genuine but moderate-severity memory-safety defect whose practical reach depends on GPAC being deployed in an RTP-consuming configuration.
Rendering a crafted PDF with Freedesktop Poppler 26.07.0 can trigger a signed integer overflow in the TrueType font handler FoFiTrueType::mapCodeToGID when an embedded font supplies a manipulated segCnt value, producing a crash or a bounded out-of-bounds read rather than confirmed code execution. The flaw is remotely reachable with no authentication (CVSS 4.0 PR:N, CVSS 3.1 PR:N) but requires the victim or an automated pipeline to open or convert the attacker-supplied document (UI:P/UI:R), so it is not a hands-off network exploit; publicly available exploit code exists but there is no indication of confirmed active exploitation (no CISA KEV listing). With a base score of 5.3 and C:L/I:L/A:L on the assessed 3.1 vector, this is a moderate, opportunistic-risk issue rather than a top-tier priority, and it matters most to environments that automatically render or convert untrusted PDFs at scale.
NUUO Network Video Recorder 2.0.0 is vulnerable to arbitrary file read. In up.php, the url parameter submitted by the user via POST is received, and fopen() is used to open the URL in binary read-only mode. The content is then written to the /tmp/ directory, with the filename derived from basename() of the URL. This operation requires no authentication.
Imager versions from 0.45_02 before 1.035 for Perl read outside the EXIF block via unchecked start offsets in tiff_load_ifd. tiff_load_ifd() validates an IFD entry's data by checking that `entry->offset + entry->size` stays within the EXIF block, and never checks the start offset itself. Where that sum is not the real end of the data, the check passes with the entry starting outside the block. Through 1.032 `entry->offset` is a plain int, so on the usual two's-complement implementations an offset with the high bit set converts to negative and the sum can land back inside the block. From 1.033 the field is a size_t and the addition wraps only where size_t is 32 bits. The IFD's own start offset is checked the same way and wraps where unsigned long is 32 bits, which includes 64-bit Windows. Any caller of Imager->read() on an attacker-supplied image may receive EXIF tags holding bytes from outside the block, or crash the process.
Heap out-of-bounds read in the PoDoFo C++ PDF library (versions 1.0.0 through 1.1.0) lets a crafted PDF containing an Indexed color-space image cause the library to read past the end of its palette lookup buffer. An attacker must convince a victim to hand the malicious PDF to an application built on the affected library and have that application decode or render the embedded Indexed image; no authentication is required (CVSS 4.0 vector PR:N, AV:L, UI:P), and the practical impact is dominated by a process crash leading to denial of service, with only adjacent heap bytes potentially disclosed rather than targeted secret exfiltration. Exploitation yields a limited confidentiality gain and a high availability impact; no public exploit code has been identified at time of analysis and there is no CISA KEV entry. The flaw is fixed in PoDoFo 1.1.1.
Cross-origin information disclosure in Google Chrome (through the bundled Skia graphics library) affects versions prior to 153.0.8010.52, where improper state validation lets a crafted HTML page cause the renderer to expose data belonging to another origin. Exploitation requires the victim to load an attacker-controlled page (UI:R) and yields only partial confidentiality impact - no code execution, data modification, or denial of service - which is why the CVSS base score is a modest 4.3. No public exploit code has been identified at time of analysis, CISA SSVC rates exploitation as none and automatable as no, and the vendor has released a fixed build, so this should be treated as a low-priority, patch-routinely item rather than an emergency.
UI spoofing in Google Chrome's WebAppInstalls component (versions prior to 153.0.8010.52) lets a remote, unauthenticated attacker misrepresent interface elements to a user who visits a crafted HTML page, but only if the victim is successfully socially engineered into trusting the falsified prompt. Exploitation requires mandatory user interaction (CVSS UI:R) and produces only a limited integrity impact - no code execution, no data exfiltration, and no availability loss - which is why Chromium rates it Low severity. No public exploit code has been identified at time of analysis, CISA SSVC records no exploitation and rates the issue non-automatable with partial technical impact, and the vendor has released a patch in Chrome 153.0.8010.52.
Information disclosure in the Paint component of Google Chrome desktop allows unauthenticated remote attackers to obtain sensitive information when a victim renders a crafted HTML page, per CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N (6.5). Exploitation is gated by mandatory user interaction (UI:R), keeping it out of the automatable category under CISA's SSVC assessment (Exploitation: none, Automatable: no, Technical Impact: partial), and no public exploit code has been identified at time of analysis. The confidentiality-only impact - no integrity or availability effect, no code execution or sandbox escape reported - makes this a genuine but modest issue rather than an urgent priority; Google has released a fixed build, so exposure ends once Chrome is updated to 153.0.8010.52 or later.
Cross-origin information disclosure in Google Chrome's Permissions implementation allows a remote attacker to leak data across origin boundaries when a victim opens a crafted HTML page in Chrome versions prior to 153.0.8010.52. Exploitation requires user interaction (the victim must load the page) but no authentication or special privileges, and the impact is limited to low-sensitivity data exposure (CVSS 4.3, Chromium severity Medium). No public exploit code or confirmed active exploitation was identified at time of analysis, and the auto-updating Stable channel sharply narrows the exposure window once 153.0.8010.52 propagates.
Memory disclosure in Google Chrome prior to 153.0.8010.52 allows a local attacker to read out-of-bounds data through the browser's DataTransfer implementation, with the sandbox-crossing scope change (S:C) in the CVSS vector indicating the leaked memory can originate outside the renderer process rather than from within the attacker's own context. Per the assessed vector (AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N, base 6.3) exploitation requires the attacker to already be running a local program on the victim's machine and to use social engineering to obtain user interaction, and it produces only confidentiality impact with no integrity or availability effect, so this is an information-disclosure bug rather than a sandbox escape or code-execution primitive. There is no public exploit code identified at time of analysis and the issue is not confirmed actively exploited (it is not in CISA KEV); Google has shipped version 153.0.8010.52, which resolves the flaw.
Uninitialized heap memory disclosure in OpenSlide occurs because libtiff 4.7.1 changed how the indirect TIFF tile read path handles a partial bottom tile row, causing _openslide_tiff_read_tile() to request a full tile-height destination and pull uninitialized heap bytes into pixel data returned by openslide_read_region(). Only OpenSlide 4.0.0.10 and 4.0.0.11 official binary builds - or any OpenSlide build linked against libtiff 4.7.1 or newer - are affected, and exploitation requires a network service that renders attacker-supplied, non-NDPI TIFF-based whole-slide images; OpenSlide linked against libtiff 4.7.0 or earlier is explicitly not affected, and reliability of any actual data extraction depends on downstream pixel transparency handling and recompression, so the practical leak is limited and uncertain. No public exploit code was identified at time of analysis, and the issue is fixed in OpenSlide 4.0.1 and official binary build 4.0.0.12.
Command injection and arbitrary file truncation in the Perl GD module before 2.86 (perl-gd 2.86-r0 on Alpine) arise because GD::Image's _make_filehandle helper opened filenames using Perl's two-argument open(). When an application passes an attacker-influenced filename to constructors like GD::Image->new or newFrom*, prefixes such as `cmd |`, `| cmd`, or `> file` are interpreted by Perl as a command pipe or redirect, yielding command execution or destructive file truncation. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV; EPSS is 0.26% (50th percentile).
Qt6 WebEngine (qt6-qtwebengine) on Alpine Linux has been patched in package version 6.10.1-r7, addressing an unspecified vulnerability. The nature, severity, and exploitability of the underlying flaw are not disclosed in available intelligence - no CVE description, CVSS score, CWE classification, or vendor advisory narrative has been published at time of analysis. Alpine Linux is the sole reporting source, and the fix is confirmed present in the Alpine package repository at version 6.10.1-r7.
Active exploitation confirmed by CISA KEV affects qt6-qtwebengine on Alpine Linux, with the vulnerability addressed in package version 6.9.1-r3. The specific vulnerability class and technical mechanism are not disclosed in available intelligence - the only confirmed data point beyond KEV status is the Alpine Linux package fix designation. Despite CISA KEV confirmation, the EPSS score of 0.25% (49th percentile) is notably low, indicating exploitation is targeted rather than widespread or automated. Any application or system running Alpine Linux with qt6-qtwebengine prior to 6.9.1-r3 should be treated as at risk given the confirmed exploitation status.
Integer underflow (CWE-191) in Netatalk, the open-source Apple Filing Protocol (AFP) server, allows a network-authenticated attacker to trigger memory corruption that may result in information disclosure, arbitrary code execution, or denial of service. The vulnerability affects versions prior to 4.4.3 and is patched in Netatalk 4.4.3 (Alpine Linux package 4.4.3-r0). No public exploit code or active exploitation via CISA KEV has been identified at time of analysis.
Confirmed actively exploited vulnerability in qt6-qtwebengine on Alpine Linux has been patched in package version 6.10.1-r2. Qt6 WebEngine is a Chromium-based web content rendering component embedded in Qt6 applications; vulnerabilities in this component typically affect any application that renders untrusted web content. Despite CISA KEV confirmation of active exploitation, the EPSS score of 0.30% (53rd percentile) suggests exploitation has been targeted rather than widespread, warranting urgent patching prioritization nonetheless.
Netatalk on Alpine Linux contains an unspecified vulnerability addressed by the Alpine package maintainers in version 4.4.3-r0. The nature of the flaw, affected attack surface, and impact have not been disclosed in the available intelligence - the sole data point is the vendor-issued Alpine Linux package fix. Security teams should treat this as a pending-disclosure patch event and apply the update while awaiting a full CVE write-up.
JWT signature verification weakness in the Cacti network monitoring framework (fixed in 1.2.31) lets an authenticated low-privilege user forge or tamper with JSON Web Tokens whose signatures are not properly validated, undermining token integrity. The CWE-347 root cause combined with the vendor's 'Jwt Attack' and 'Information Disclosure' tags points to token forgery that can bypass intended authorization checks. There is no public exploit identified at time of analysis and the flaw is not listed in CISA KEV; it was reported through the Alpine Linux vendor channel and patched upstream by the Cacti project.
Client-side memory corruption in FreeRDP (all versions before 3.27.1) lets a malicious or compromised RDP server compromise a connecting client through improperly bounds-checked bitmap cache orders. The cacheId field of Cache Bitmap V2/V3 orders was masked to only two bits (0x0003) instead of three (0x0007) and used to index cell-cache arrays without validating it against the negotiated number of cells, enabling out-of-bounds access controlled by the server. There is no public exploit identified at time of analysis and EPSS is low (0.45%, 36th percentile), but the CVSS 8.8 reflects full confidentiality, integrity and availability impact once a user connects to the attacker's server.
Trailing whitespace at the end of a selector string makes Dasel 3.0.0 through 3.11.1 read past the end of its input and panic with an index-out-of-range error, terminating the process - an availability-only denial of service. The trigger is trivially small (dasel query 'a ', or a selector ending in a tab or newline) and is reachable both from the command line and from the Go library entry points dasel.Query and lexer.NewTokenizer(...).Tokenize(), so any embedding application that forwards caller-influenced selector text into Dasel can be crashed. The assessed impact is local and unauthenticated with high availability impact and no confidentiality or integrity effect (CVSS 6.2), no public exploit code was identified at time of analysis, and version 3.11.2 is the fixed release.
Username enumeration is possible against Tinyauth instances running versions before 5.1.0 because the local-user login handler and the HTTP basic-auth middleware return as soon as an account is reported missing, while an existing account triggers a comparatively slow bcrypt password verification, leaving a remotely measurable timing discrepancy (CWE-208). Unauthenticated attackers with network reach to the authentication endpoints can take repeated latency measurements and statistically distinguish valid local usernames from invalid ones; the independent assessment rates this CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N, so the outcome is limited to disclosure of valid usernames with no direct password, session, or data compromise, and exploitation is constrained by network/server jitter requiring many samples. Deployments that authenticate exclusively through external OAuth/OIDC providers and maintain no local users do not exercise the vulnerable bcrypt path, and no public exploit code was identified at time of analysis; the vendor-released fix is version 5.1.0.
Authenticated, low-privileged users of GoCD before 26.1.0 can retrieve source-control credentials in cleartext from several read-only pipeline and material APIs whose responses fail to mask the userinfo portion of material URLs. Exposure is narrow: it only affects legacy configurations where an administrator embedded a username and password directly in a material URL, while credentials held in GoCD's dedicated password fields or secret-management plugins stay encrypted and are not disclosed by this issue. The CVSS 4.0 base score of 2.3 reflects the uncommon prerequisite configuration (AT:P) and limited confidentiality impact, and no public exploit code or confirmed active exploitation has been identified at time of analysis.
Logout in Apache Airflow Core API versions before 3.3.2 silently fails to revoke the caller's credential when it is presented as an `Authorization: Bearer` header rather than the browser `_token` session cookie, returning a normal logout response while nothing is invalidated. The token therefore stays usable until its natural expiry, 24 hours by default and configurable, so an authenticated attacker who already holds a copy of that token keeps the victim's access after the victim has logged out and believes the session ended; no privileges beyond the victim's own are obtained and obtaining the token is outside the scope of this issue. There is no public exploit identified at time of analysis and no confirmed active exploitation - the flaw is assessed as low severity (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N) precisely because it is strictly gated on the attacker already possessing a valid token that this endpoint cannot mint or steal.
Information disclosure in Apache Airflow's `/assets/events` REST endpoint lets an authenticated user who holds asset-read permission enumerate asset events - source Dag ID, task ID, run ID, timestamps, and total existence counts via pagination - for Dags they have no authorization to read. The endpoint applied no per-Dag readability filter, and because the same filter was missing from the count query, `total_entries` alone revealed the existence of hidden Dags. Affected deployments are apache-airflow versions prior to 3.3.2, and the exposure matters only where per-Dag access control is used to separate teams or tenants; in single-tenant deployments every user is already authorized to see all Dags, so nothing new is disclosed. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (CISA KEV), so this is a modest-severity broken-authorization flaw rather than a high-urgency issue. Vendor-released patch: apache-airflow 3.3.2.
MidnightBSD's mport package manager before 2.7.8 trusts the TMPDIR environment variable when extracting package metafiles, so an attacker who can influence the environment of a privileged (root or setuid/setgid) mport invocation can redirect temporary metadata extraction into a location they control. Exploitation requires a local foothold on a MidnightBSD host, a privileged mport run that inherits the attacker-supplied environment, and success in the extraction timing window, which keeps this a low-to-moderate-risk local path-integrity issue rather than a remotely exploitable flaw; no public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis. The issue is fixed in mport 2.7.8 via upstream PR 123 (commit 3790fa4), which ignores unsafe TMPDIR values in privileged contexts and rejects empty TMPDIR.
Unauthenticated price tampering in the RestroPress WordPress plugin (versions before 3.4.6) lets any remote attacker alter the client-supplied add-on price when items are added to or updated in the cart, then place an order at an arbitrary - including zero - total. The flaw is a server-side validation failure affecting only sites that run RestroPress with online ordering/cart-and-checkout enabled and paid item add-ons configured; no credentials or user interaction are required and default configurations of the affected versions are exploitable. Impact is limited to integrity of pricing/billing (CVSS 5.3, C:N/I:L/A:N) rather than data disclosure or code execution, and no public exploit code or confirmed active exploitation has been identified at time of analysis.
Improper control of resource identifiers in Omega Solution HRM OS (versions up to 20260717) allows an authenticated low-privilege user to enumerate the permission mappings of arbitrary roles by manipulating the roleId parameter of the /role-permission/permission endpoint. The outcome is confidentiality-only: role and permission metadata can be read, but no data can be modified and no code can be executed, and the CVSS v4.0 base is only 2.1 (assessed CVSS v3.1 4.3, AV:N/AC:L/PR:L/UI:N/C:L/I:N/A:N). Publicly available exploit code exists (PoC referenced via VulDB and the linked GitHub issue), but there is no confirmed active exploitation (not in CISA KEV); the vendor was contacted early and did not respond, and no vendor-released patch has been identified at time of analysis.
Information disclosure in ScadaBR up to and including version 1.1 allows an attacker to pull the complete project export - data sources, data points and graphical views - by invoking the unprotected EmportDwr.createExportJSON DWR method through /ScadaBR/export_project.htm. The vendor's CVSS 4.0 vector lists PR:N, but the fix adds Common.getUser() plus Permissions.ensureAdmin(), which indicates the endpoint executes inside an authenticated session, so realistic exploitation requires a valid low-privilege ScadaBR account rather than true anonymous access; impact is confined to read-only configuration disclosure with no integrity or availability effect. Publicly available exploit code exists and the issue is fixed in ScadaBR 1.2.0, though there is no confirmation of active exploitation.
Information disclosure in nvm versions before 0.40.8 allows a local attacker who controls a repository to read arbitrary files readable by the invoking user when the developer runs `nvm use`, `nvm install`, or `nvm which` with a crafted `.nvmrc`, or when the user manually runs `nvm alias` with a traversing name. The path traversal in alias resolution causes nvm to print non-comment lines from the opened file in an error message; the automated `.nvmrc` route exposes only the first non-comment/non-empty line, while the manual `nvm alias` route can expose all such lines. No public exploit code or active exploitation has been identified at time of analysis, and the vendor addressed the issue in nvm 0.40.8.
Integer underflow in the PE parser of Manalyze 1.0.0 (PE::_parse_debug in manape/pe.cpp) can be triggered when the tool processes a crafted Portable Executable whose IMAGE_DEBUG_MISC debug-directory entry declares a Length smaller than the misc structure header, causing the computed string length to wrap to a very large unsigned value and the parser to read beyond the intended buffer. Exploitation is not remote in practice: it requires a local user (typically a malware analyst) to voluntarily run the unpatched Manalyze CLI against the malicious sample, so the assessed risk is low (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L), with impact largely confined to the parsing process - the tag 'Information Disclosure' reflects the out-of-bounds read potential rather than confirmed data exfiltration. No public exploit code and no active exploitation have been identified at time of analysis, and an upstream fix commit (3e299685759f4f767088871de58c5d07f98ee382) is available.
Information disclosure in D-Link DIR-X1860Z routers running firmware up to 1.0.2.220120.165402 lets unauthenticated users on the same local network segment read sensitive data through two ubus JSON-RPC handlers, routerd.wificfg_get and routerd.get_rand_key. The bug is reachable only from the adjacent network (LAN, guest WiFi, or a compromised local device) and carries low confidentiality impact with no integrity or availability effect, and no public exploit identified at time of analysis. D-Link ships a HOTFIX firmware (1.0.7.260821.161908) that resolves the issue, but the DIR-X1860Z is an end-of-life product, so exposure is concentrated on unpatched units still in service.
Hardcoded default secrets and credentials in aiyiyi121 SxDevOps 1.0/1.1 let unauthenticated remote attackers obtain sensitive information from instances that still run the shipped defaults - a Django SECRET_KEY of 'change-me' and the documented demo/admin password (for example Admin@123456) published in the project README. The issue is CWE-200 (exposure of sensitive information), rated CVSS 4.0 6.9 with confidentiality-only impact; no public exploit code has been identified at time of analysis, and any operator who set a strong SECRET_KEY, changed the admin/demo password, or disabled the demo accounts before exposing the service is not affected, so realistic risk is confined to negligently configured default installs of a niche self-hosted tool. The vendor was contacted early and issued a fix in commit 2b4bf8585c3e731e7a8af30801ea46680bc783f9.
Information disclosure in the Meow Gallery WordPress plugin before 5.5.5 lets authenticated users holding Author-level access or higher pull back metadata - titles, authors, dates and publish statuses - belonging to other users' draft and private posts. The vulnerable post-data retrieval routine performs neither a proper capability check nor owner-scoping of results, so a low-trust Author account on a multi-author site can enumerate unpublished content it was never meant to see; post bodies themselves are not exposed and there is no write, modify or denial-of-service impact. A publicly available exploit code exists, but the flaw is not confirmed actively exploited (no CISA KEV listing), and the risk is genuinely low-priority: it is not reachable by anonymous visitors, requires a valid Author-or-higher login (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N in our assessment), and matters mainly on sites where lower-trust Author accounts coexist with genuinely sensitive unpublished material.
Non-privileged applications running on a ZTE nubia Z80 Ultra (NX741J) smartphone can retrieve the device's Wi-Fi MAC address by querying the read-only factory_mac_address field exposed through the Android Settings.Secure content database, defeating the platform's normal restriction on hardware MAC address access. The issue is purely local (assessed CVSS:3.1/AV:L/AC:L/PR:N/UI:N, base score 3.3, C:L/I:N/A:N), requires an attacker-supplied app to already be installed and executing on the handset, and leaks only a single low-sensitivity hardware identifier whose main value is device tracking rather than data compromise. According to available intelligence, no public exploit has been identified at time of analysis and the CVE is not listed in CISA KEV; deployment is limited to a single consumer handset model, which keeps overall risk low.
Filter bypass in PHP-FTS (olivier-ls/php-fts) through version 1.1.3 allows an authenticated remote attacker to defeat document-scoping filters used by consuming applications for ownership or multi-tenant isolation, exposing search results the application intended to hide. The flaw resides in SearchEngine::matchesSingleFilter in src/SearchEngine.php, where filter values were compared with loose `==` and non-strict `in_array()`; because PHP treats any non-empty string as equal to boolean true, a filter value of true matched every document with a non-empty value in that field, and the string '42' matched the integer 42, enabling retrieval of other users' or tenants' records. Publicly available exploit code exists (a proof-of-concept write-up is referenced alongside the CVE from VulDB and a GitHub PoC repository), and the issue is not listed in CISA KEV, so no confirmed active exploitation is known; the risk is context-dependent and moderate, materializing only where the application relies on PHP-FTS filters as an access-control boundary and passes untyped request input directly into filter construction.
A use-after-free memory-safety flaw in Exim before 4.100.1 can crash the mail transfer agent process when the daemon is compiled against the GnuTLS TLS backend and configured with certain non-default TLS settings; once a vulnerable server is reachable over the network, no authentication (PR:N) or user interaction (UI:N) is required, but the CVSS vector reflects high attack complexity (AC:H) because the triggering configuration is unusual and non-default. The assessed impact is availability-only (C:N/I:N/A:L) - a crash or degraded service rather than code execution or data exposure. There is no confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis, so practical risk is confined to the narrow subset of Exim deployments using GnuTLS with the specific triggering TLS options.
Credential exposure in OpenPanel's Model Context Protocol (MCP) integration causes MCP authentication tokens supplied as URL query parameters to be written verbatim into plaintext application logs, letting anyone who can read application stdout, container/pod logs, or a centralized logging/SIEM store harvest base64-encoded credentials and replay MCP requests for read access to project analytics. The issue is gated by prior read access to the log data (CVSS 4.0 vector AV:L/PR:L; the independent assessment scores it low at CVSS 3.1 with only low confidentiality impact and no integrity or availability effect), so it is a real but low-priority defect rather than a remote unauthenticated path. No public exploit identified at time of analysis, and no confirmed actively exploited (CISA KEV) status is indicated in the provided data.
Unauthenticated information disclosure in the WordLift - AI powered SEO - Schema plugin for WordPress affects all versions up to and including 3.54.10, allowing remote attackers with no credentials to harvest the title, body content, author, publication and modification dates, word count, comment count, and other metadata of private, draft, and pending posts. The flaw stems from the plugin's /wordlift/v1/jsonld/ REST routes being registered with a permission_callback of '__return_true', combined with a downstream JSON-LD converter that calls get_post() without validating post status or the caller's capabilities, so sequential post-ID enumeration bypasses WordPress core access controls. No public exploit code was identified at time of analysis and the vulnerability is not reported as actively exploited; the CVSS 3.1 base score of 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) reflects a confidentiality-only, low-complexity disclosure with no integrity or availability impact.
Any authenticated WordPress user holding contributor-level capabilities or higher can pull the entire customer dataset out of the Easy Appointments plugin (all versions up to and including 3.12.27) because the handle_customers_ajax handler returns ea_customers records without enforcing an adequate capability check. The exposed records contain personally identifiable information such as names, email addresses, mobile numbers, dates of birth, and physical addresses, so the impact is a high-confidentiality, read-only disclosure with no integrity or availability effect, consistent with the assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N score of 6.5 (MEDIUM). Exploitation is not possible for unauthenticated visitors - an attacker must first hold a low-privilege account - and no public exploit identified at time of analysis; risk is concentrated on multi-author sites, membership sites, or any installation that hands out contributor accounts or has self-registration mapped to elevated default roles.
Unauthenticated information disclosure in the Bread WordPress plugin (versions up to and including 2.9.12) lets any remote visitor read the plugin's entire configuration export, including the PDF protection password stored in plaintext, by simply requesting the /?export-meeting-list=1 endpoint. The flaw is trivially reachable: the download_settings function is registered on the plugins_loaded hook and explicitly permits execution on non-admin public pages, so no authentication, authorization, or user interaction is required (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U, base 5.3 MEDIUM). Impact is bounded to disclosure of the stored protection_password rather than site credentials or code execution, and no public exploit code has been identified at time of analysis; the practical risk depends on how sensitive the protected PDF meeting lists and their shared password are in a given deployment.
Missing authorization in the Nimble Page Builder WordPress plugin through 3.3.8 lets an authenticated user with only Subscriber-level access read the page-builder content of arbitrary non-public posts and pages, including drafts, pending, private and scheduled items. The plugin's authenticated AJAX action returns stored page-builder content without verifying that the requester is allowed to edit the target post, so an attacker can enumerate post IDs and exfiltrate unpublished content; publicly available exploit code exists and the WPScan disclosure serves as the entry point, though the issue has not been reported as actively exploited in CISA KEV. Impact is confined to information disclosure (CVSS 3.1 4.3, C:L only, PR:L, no integrity or availability effect), and sites that allow open user registration effectively lower the bar to any remote registrant.
Unauthenticated attackers can impersonate the Better Messages plugin's own internal AI bot accounts on WordPress sites running versions up to and including 2.15.33, gaining entry to administrator-restricted chat rooms and reading the private message history of other users. The flaw is entirely pre-authentication (CVSS vector PR:N/UI:N) and requires only that unauthenticated guest registration is enabled and that the server forwards the client-supplied X-Real-IP header to the plugin, which stores it verbatim; the plugin's is_ai_bot_user() check then prefix-matches the attacker-chosen value against 'ai-chat-bot-'. No public exploit code was identified at time of analysis and there is no CISA KEV confirmation of active exploitation, but the low complexity and lack of any credential requirement make the issue straightforward to abuse where restricted rooms exist. The vendor-assigned score is 5.3 (Medium, C:L/I:N); our reassessment raises confidentiality to High and adds a Low integrity impact because the same bypass allows posting into restricted rooms, netting a materially higher severity than the published vector implies.
Sensitive information disclosure in the Divi Essential WordPress plugin through version 5.8.1 allows any authenticated user holding Subscriber-level access or above to enumerate every table in the site's WordPress database and read a caller-controlled number of rows from each, exposing usernames, emails, hashed passwords, session tokens, secret keys, and plugin-stored API credentials. The flaw is trivially reachable because the dnxte_get_database_tables and dnxte_get_database_data AJAX handlers only perform a nonce check when the 'nonce' POST parameter is supplied - omitting it skips the check entirely - and no current_user_can() capability enforcement exists. Authentication requirements are confirmed as low-privileged (CVSS PR:L) rather than unauthenticated, so the practical attack surface depends on whether the site allows open user self-registration; no public exploit code was identified at time of analysis, and the impact is confidentiality-only with no modification of data or loss of availability.
Local file disclosure in Calculator Lock for Android allows a local actor with shared external storage access, such as an authorized non-root ADB shell or a co-resident file-reading app, to copy the vault's SQLite database and media files without entering the calculator passcode. The published CVSS is 6.8, and the independent assessment (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) confirms high confidentiality impact with no integrity or availability impact; the passcode still gates the in-app UI. The independent assessment classifies this as a genuine but low-urgency local issue, and no public exploit identified at time of analysis.
SIP body-length truncation in Suricata 8.0.0 through 8.0.5 causes the IDS/IPS engine to expose only the first 65,536 bytes of oversized SIP request or response bodies to frame-based inspection, letting an unauthenticated remote attacker hide malicious content in the omitted remainder and evade detection. The flaw resides in the Rust SIP parser, which stores body offsets and lengths in 16-bit fields, so any body larger than 65,536 bytes wraps the stored length; this only matters on deployments that enable SIP application-layer parsing and run rules referencing frame:request.body or frame:response.body, and it degrades detection integrity only (no crash, no code execution, no data exposure). Per the CVSS vector (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N, score 3.7) the impact is limited to integrity of the detection pipeline, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Unauthenticated information disclosure in CordysCRM (1Panel-dev) versions prior to 1.7.2 lets any network-reachable caller retrieve CRM form metadata via GET /mcp/form/config/{formKey}, exposing field names, types, required flags, default values, options, validation rules, and binding sources. The flaw exists because ShiroFilter marks the /mcp/** path as anonymous and McpController.getMcpField carries no permission annotation, so the endpoint is reachable without credentials (CVSS 4.0 base 6.9; independent assessment CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N). Impact is limited to schema/metadata disclosure rather than direct access to customer records, and no public exploit code has been identified at time of analysis; exploitation does require knowledge or brute-forcing of valid formKey identifiers.
A local time-of-check/time-of-use (TOCTOU) race condition in cockpit-files on Red Hat Enterprise Linux 9 and 10 allows an unprivileged local attacker to redirect a privileged chown operation to an arbitrary file by replacing a newly created directory with a symlink, resulting in potential information disclosure or unauthorized modification of sensitive files. Exploitation requires a privileged operator to trigger directory creation with owner assignment via cockpit-files inside an attacker-controlled writable parent directory, and the attacker must win a narrow timing window (CVSS 3.1: AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N, 6.0). No public exploit code or confirmed active exploitation was identified at time of analysis; this is a modest-priority local privilege/integrity issue rather than a mass-exploitation threat.
HTTP request smuggling in IBM WebSphere Application Server and WebSphere Application Server Liberty - as bundled in IBM CICS TX Advanced per the affected CPE - lets remote attackers desynchronize request framing between a front-end intermediary and the WebSphere back end, enabling request tampering or response poisoning. Exploitation requires the server to sit behind a reverse proxy, load balancer, or CDN that parses Content-Length/Transfer-Encoding framing differently than the back end; no authentication or user interaction is needed (PR:N/UI:N), but attack complexity is high (AC:H) because the attacker must find and reliably trigger a specific parser discrepancy in the real deployed chain, and a directly exposed server with no divergent front-end parser is not smuggle-able. Impact is bounded to low confidentiality and integrity with no availability effect (CVSS 3.1 base 4.8); this is a genuine but modest-severity issue rather than a top priority, and no public exploit was identified at time of analysis.
HTTP request smuggling in IBM WebSphere Application Server 8.5 can allow unauthenticated remote attackers to desynchronize request processing when the server sits behind or in front of an HTTP intermediary with mismatched Content-Length parsing, potentially leading to credential theft, cache poisoning, or request hijacking. The flaw (CWE-444) rates 6.5 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N) and requires a specific proxy-layer mismatch and concurrent traffic; no public exploit identified at time of analysis. Vendor patch is available and the risk is assessed as moderate and non-urgent.
HTTP request smuggling in IBM WebSphere Application Server Liberty - the runtime bundled with IBM CICS TX Advanced 10.1 - lets remote, unauthenticated attackers desynchronize HTTP message framing between an upstream HTTP parser and the Liberty backend, so a smuggled request can be processed as if it came from the trusted front-end, with low confidentiality and integrity impact on subsequent requests sharing the connection. Exploitation requires a multi-tier topology (reverse proxy, load balancer, or CDN in front of or behind Liberty) where the two parsers disagree on Content-Length/Transfer-Encoding or chunked framing, and is rated high complexity because the specific parsing gap must be discovered and precisely crafted while connection reuse must be achievable; no user interaction is required. Risk is moderate and consistent with the vendor CVSS of 4.8 (Medium); no public exploit identified at time of analysis, and patch is available from the vendor.
In libsmpp35 from 0.1.0 through 1.8.0 out of bound read issue was found in the at smpp34_unpack() function via attacker controlled SMPP PDUs, leading to memory corruption.
Local information disclosure in cockpit-machines on Red Hat Enterprise Linux 9 and 10 allows an authenticated local user to read plaintext VM credentials - including passwords - that the component passes directly on process command-line arguments during VM creation or installation. Exploitation is timing-dependent: the secret is only readable while a provisioning operation is in flight, and it also requires that /proc process arguments remain visible to other users (i.e., the host is not hardened with a hidepid-style mount option), so risk concentrates on multi-user or shared virtualization hosts. It yields no code execution and no privilege escalation, but a disclosed password compromises access to the affected VM; no public exploit code has been identified at time of analysis and the flaw is not confirmed actively exploited (not in CISA KEV).
Local information disclosure in cockpit-machines on Red Hat Enterprise Linux 9 and 10 allows an authenticated local attacker who can enumerate other users' process arguments to read guest VM installation credentials such as rootPassword and userPassword. The credentials are passed by install_machine.py as a JSON command-line argument during VM creation, so exposure is limited to the window while an administrator's installation workflow is running and depends on the host's process-visibility policy (e.g. /proc without hidepid=2). Publicly available exploit code exists, but there is no confirmed active exploitation; the issue requires local access plus a concurrently active install and cannot be triggered remotely or unauthenticated.
Local information disclosure in the cockpit-machines package on Red Hat Enterprise Linux 9 and Red Hat Enterprise Linux 10 lets an unprivileged local user capture a Red Hat Subscription Management (RHSM) offline token that is passed as a command-line argument to a helper script during token validation. Rated 5.0 (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N), the impact is confidentiality-only: a local account that can read other processes' metadata (for example /proc/<pid>/cmdline via ps) must catch the brief window in which a privileged operator runs the validation, and the stolen token can then be exchanged for RHSM access tokens. There is no public exploit code identified at time of analysis and no CISA KEV entry; Red Hat tracks the issue as CVE-2026-92745 (EUVD-2026-83260).
Session fixation in the password-protected shared-notes flow of SysReptor (Syslifters) before version 2026.68 lets an attacker who can plant a known, unauthenticated share-page session cookie in a victim's browser reuse that session after the victim enters the correct note password, gaining access to that shared note. The main SysReptor login is unaffected; only the 'publicshareinfo-auth' / 'sharednote-detail' share flow fails to rotate the session identifier on successful authentication (CWE-384). Exploitation requires a separate cookie-injection capability (for example an XSS vector, a shared or attacker-controlled device, or a network man-in-the-middle position) plus precise knowledge of the shared-note URL the victim will authenticate against, and the victim must actively submit the password, so the assessed CVSS 3.1 score is 3.7 (AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N); no public exploit code was identified at time of analysis.
Unauthenticated holders of a SysReptor public note share link can retrieve project-wide collaborative-editing metadata for any deployment running a version prior to 2026.55, because the public-share WebSocket consumer joins the same collaboration group as authenticated project members and forwards client-information, connect/disconnect, awareness, and deletion events without restricting them to the shared note subtree. This leaks project member usernames and display names plus the identifiers and live editing activity of notes that were never shared; note content itself stays protected and no write access is granted. Our reassessment rates the issue CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N (5.3), higher than the vendor-assigned 3.5 (PR:L/UI:R) because the metadata is returned to an unauthenticated share-link holder on connection, though exploitation still requires possession of a valid share link. There is no public exploit code and no confirmed active exploitation (CISA SSVC exploitation: none); the fix is included in release 2026.55 via commit 1e52e5058b0c7f420dc45c87ad72e7a4585477b1.
AnyCable (anycable-go) through 1.6.14 ships its telemetry subsystem enabled by default with a hardcoded public auth token ('secret' in telemetry/config.go) and derives its cluster fingerprint by hashing the full configuration file plus raw os.Args, which can include values passed via --secret, --jwt_secret, and --http_rpc_secret; an adversary who can MITM or DNS-hijack telemetry.anycable.io can intercept the outbound telemetry POST, and because the client's token is publicly known it offers no protection. The transmitted clusterFingerprint is a SHA256 digest rather than raw plaintext, so meaningful secret recovery additionally depends on low-entropy secrets, and the required network-interception position makes this a moderate-to-low real-world risk best characterized as a hardcoded-credential and telemetry-exposure design flaw rather than a directly exploitable credential leak. Exploitation status: no public exploit code identified at time of analysis and no confirmed active exploitation (CISA KEV); the GHSA advisory documents only a conceptual DNS-spoofing reproduction. Vendor-released patch: 1.6.15.
Unauthenticated remote attackers can query the SNMP v2c service on Grandstream GWN7660ELR access points running firmware before 1.0.27.6 when the service is left with the factory-default community string 'public', harvesting system metadata such as OS and kernel versions, process names and command-line arguments, interface configuration, routing and ARP tables, active TCP connections, and filesystem paths. The CVSS 4.0 base score is 6.9 (vector CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N) and our independent assessment maps it to CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N - a read-only reconnaissance issue requiring only UDP/161 reachability, with no write, code execution, or lateral-movement primitive on its own. No public exploit code has been identified at time of analysis and the CVE is not in CISA KEV, so this is a genuine but modest-priority information-disclosure weakness whose real-world exposure depends on whether SNMP is enabled, still using the default community string, and reachable from untrusted networks; it is fixed in firmware 1.0.27.6.
File-system information disclosure in IBM WebSphere Application Server 9.0 and 8.5 lets an attacker positioned on an adjacent network segment query the FileTransfer servlet and learn details about the server's file system, such as file and directory names or paths. Per the vendor-supplied vector (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, base 4.3), the flaw is rated unauthenticated and requires no user interaction, but the adjacent-network precondition means the attacker must already sit on the same management/admin LAN or WebSphere Network Deployment segment rather than reaching the service from the open Internet, and impact is limited to low-confidentiality disclosure with no integrity or availability effect. No public exploit code has been identified at time of analysis, and the CVE is not listed in CISA KEV; overall this is a low-priority issue, though it is notable because WebSphere is widely deployed in large enterprises.
Cross-site request forgery token recovery in the Mojolicious Perl web framework (all versions prior to 9.48, tracked as cpe:2.3:a:mojolicious:mojo) lets an unauthenticated attacker recover a victim's per-session CSRF token through a BREACH compression side channel and then forge cross-site requests that pass csrf_protect. The attack only works in deployments that enable HTTP response compression and render the token into HTML (via csrf_field, csrf_token, or csrf_protect) while reflecting attacker-influenced content in that same compressed response; API-only deployments that never emit the token in HTML are explicitly unaffected. It is a high-effort, victim-interaction-dependent attack (CVSS 4.2, AC:H/UI:R) with no public exploit identified at time of analysis, and the vendor has shipped a fix in version 9.48 that masks the token with fresh randomness on every request.
HTTP request smuggling (CWE-444) in IBM WebSphere Application Server 8.5, 9.0, and Liberty lets an authenticated, low-privileged remote attacker desynchronize HTTP request framing between WebSphere and an intermediary so that one user's request boundaries are misattributed on a shared connection. The issue only manifests when WebSphere sits behind or in front of a second HTTP parser (reverse proxy, load balancer, or CDN) that disagrees with WebSphere on Content-Length versus Transfer-Encoding chunked handling; a standalone WebSphere instance with no fronting or backend HTTP hop is not affected, and the 4.2 score reflects high attack complexity, partial confidentiality and integrity impact, and no availability or scope change. No public exploit code and no confirmed active exploitation were identified at time of analysis, and a vendor patch is available per IBM's advisory.
Heap out-of-bounds read in libheif prior to 1.23.2 lets an application that builds inline-mask region metadata through the library's writer API leak adjacent heap memory or crash. Specifically, heif_region_item_add_region_inline_mask_data() stored a caller-supplied mask buffer without verifying that mask_data_len equals ceil(width*height/8); a later heif_region_get_mask_image() render derives the number of bytes to read from the region geometry, so an undersized buffer causes the reader to copy bytes past the end of the allocation into the returned monochrome mask image. The file-parsing/decode path validates the canonical mask size and is explicitly not vulnerable, so merely opening a crafted HEIF/AVIF file does not trigger the bug; exploitation requires a local program in which attacker-influenced geometry and mask data disagree, consistent with the assessed vector AV:L/AC:H/PR:N/UI:N (CVSS 4.0). There is no confirmed active exploitation (no CISA KEV listing), and no public exploit code was identified at time of analysis; the issue is a genuine but low-priority memory-safety defect rather than an emergency, and version 1.23.2 fixes it.
Sensitive information exposure in IBM Common Licensing Agent 9.0 through 9.0.0.2 and IBM Administration and Reporting Tool (ART) 9.0 through 9.0.0.2 allows an authenticated low-privilege user to cause error messages to reveal environment, user, or associated data details. The assessed vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N (CVSS 4.3), so exploitation requires valid authentication, has low complexity, and yields only reconnaissance-grade confidentiality impact with no integrity or availability impact. No public exploit was identified at time of analysis, and this is a low-priority information-disclosure issue rather than an actively exploited flaw.
Denial of service in OpenImageIO versions prior to 3.0.21.0, 3.1.16.0, and 3.2.0.3-beta1 occurs when the library processes a truncated TGA file while writing GIF output, triggering a signed 32-bit integer overflow in GifSplitPalette() that leads to an out-of-bounds read (CWE-125) and a process crash. The CVSS v3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H) indicates the attacker is unauthenticated (PR:N) but requires local access and user interaction, with no remote or unauthenticated network trigger. No public exploit code or active exploitation has been identified; this is a low-priority hardening issue for workflows that transcode untrusted images to GIF.
IBM Controller versions 11.0.0 through 11.0.1 FP7 and 11.1.0 through 11.1.3 FP1 send sensitive data in cleartext, allowing an attacker who occupies a man-in-the-middle position on the network path to capture confidential information. Exploitation requires an on-path adversary (e.g., via ARP or DNS spoofing or a compromised intermediary) but no authentication or user interaction; the CVSS 3.1 base score is 5.9 with high confidentiality impact but no integrity or availability impact. No public exploit code or confirmed active exploitation has been identified, and IBM has released a patch.
IBM Cognos Analytics versions 12.0.4 through 12.0.4 FP2 and 12.1.0 through 12.1.3 FP1 embed sensitive information within source code delivered to clients, allowing an authenticated user with access to that code to harvest data that can be used to mount further attacks against the system. The flaw carries a CVSS base score of 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) and requires a valid Cognos Analytics account, so exploitation is gated behind existing credentials or a foothold rather than being openly reachable; impact is limited to low confidentiality loss with no integrity or availability effect. No public exploit code has been identified at time of analysis, and the issue has not been confirmed actively exploited (CISA KEV); vendor-released remediation is available, making this a low-priority hardening item rather than an urgent threat.
Information disclosure in IBM Cognos Analytics 12.1.0 through 12.1.3 FP1 and 12.0.4 through 12.0.4 FP2 allows an unauthenticated attacker on a shared network segment to capture sensitive data because the product uses insecure network communication (CWE-327). Exploitation requires the attacker to achieve a man-in-the-middle or traffic-capture position on the same network, making it impractical over the open internet; the impact is limited to confidentiality. The vendor CVSS score of 5.9 is a fair reflection of the moderate risk, no public exploit code has been identified, and a vendor patch is available.
IBM QRadar deployments running 7.5.0 through 7.5.0 UP15 Interim Fix 006 expose sensitive backup-file contents to any holder of a valid QRadar account, because those backup files are stored with incorrect permissions. Exploitation requires authentication (CVSS vector PR:L) but no administrative rights and no user interaction, and an attacker who satisfies that bar can read configuration, credential, or event data captured in the affected backups, yielding a high confidentiality impact (C:H) with no integrity or availability effect. This is a moderate-priority information-disclosure issue rather than a high-urgency emergency: no public exploit code has been identified at time of analysis, the flaw is not in CISA KEV, and the authentication prerequisite plus the need for an unpatched interim-fix level are the principal limiting factors.
Heap out-of-bounds read in OpenImageIO's IFF image reader (src/iff.imageio/iffinput.cpp, IffInput::readimg()) affects all releases prior to 3.0.20.0, 3.1.15.0, and 3.2.0.3-beta1, allowing a caller that opens a crafted uncompressed 16-bit IFF file containing a z-buffer channel to trigger a crash or leak adjacent heap contents into the decoded image output. The flaw is an allocation/stride mismatch: the temporary scanline buffer is sized from m_header.rgba_count while the subsequent memcpy uses m_header.pixel_bytes(), whose stride also counts z-buffer bytes, producing an oversized copy. Exploitation requires local, user-initiated parsing of the malicious file (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H, 6.1) with no privileges needed but no remote zero-interaction path; no public exploit code and no confirmed active exploitation were identified at time of analysis, and EPSS/KEV data were not provided. Vendor-released patches exist in versions 3.0.20.0, 3.1.15.0, and 3.2.0.3-beta1.
Unauthenticated information disclosure affects the Multicluster Observability Addon in Red Hat Advanced Cluster Management for Kubernetes, enabling attackers on the adjacent network to access a debug endpoint that leaks goroutine, heap, and command-line profiling data. The misconfiguration originates in the underlying addon-framework library, which exposes the endpoint without requiring credentials; exploitation only requires a basic encrypted (TLS) connection. No public exploit has been identified at time of analysis, and the vulnerability does not permit remote code execution, but the exposed profiling information could aid reconnaissance or further attacks.
IBM Controller releases 11.0.0 through 11.0.1 FP7 and 11.1.0 through 11.1.3 FP1 can return detailed technical error messages to the browser, allowing remote, unauthenticated attackers to harvest implementation details about the affected system (CWE-209). Per the CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, exploitation is network-reachable and requires no credentials or user interaction, but the impact is confined to low-value information disclosure that is most useful as reconnaissance for follow-on attacks rather than for direct compromise. No public exploit code has been identified and the issue is not listed in CISA KEV, so this is a genuine but low-priority weakness whose practical risk largely depends on whether the Controller web interface is reachable from untrusted networks.
An out-of-bounds read in the Zephyr RTOS gPTP (IEEE 802.1AS) Ethernet layer lets an attacker on the same link crash-free but silently expose memory contents: a truncated Ethernet frame with ethertype 0x88F7 and fewer than 34 bytes of payload is accepted by gptp_handle_msg(), which dereferences a gPTP header pointer that extends past the received data and then retains the short packet for later state-machine parsing. Affected are Zephyr releases from 1.13.0 up to (but not including) 4.4.2 built with CONFIG_NET_GPTP on an interface configured as a gPTP port; no authentication or user interaction is required (PR:N/UI:N), though exploitation is limited by the adjacent-only vector and the requirement for a link that can deliver sub-minimum frames (for example the native_sim TAP driver or a MAC that accepts undersized frames). The impact is read-only and low (CVSS 3.1 base 3.1, C:L/I:N/A:N): under the default fixed-size buffer allocator only stale recycled buffer contents within the 128-byte fragment are disclosed, while a genuine out-of-bounds read requires the experimental CONFIG_NET_BUF_VARIABLE_DATA_SIZE allocator. No public exploit code was identified at time of analysis and the issue is not listed in CISA KEV; an upstream fix commit and vendor advisory are available.
HTTP request smuggling in Netty's HTTP/1.1 decoder (HttpObjectDecoder and the HttpRequestDecoder built on it) lets remote, unauthenticated attackers send a chunk-size line containing an embedded bare carriage return - for example `0\rX` - because strict chunk-line validation is skipped whenever the size line carries no `;` chunk extension, causing a request-boundary desync when Netty shares a connection with a second HTTP intermediary that frames the message differently. The flaw reaches every application and Red Hat product that embeds Netty, including AMQ Broker 7, AMQ Clients, Quarkus, Camel 4 for Quarkus 3, Camel for Spring Boot 4, Keycloak / Red Hat Single Sign-On, JBoss EAP 7 and 8, Fuse 7, Data Grid 8, Apicurio Registry 3 and Debezium 3, while independent assessment keeps it at CVSS 6.5 with AC:H because a standalone Netty service with no disagreeing proxy in the chain yields little practical smuggling impact. The public report includes a reproducible PoC test harness, but there is no CISA KEV listing and no evidence of active exploitation.
Imager versions before 1.036 for Perl disclose uninitialised heap memory reading a paletted image with pixel indexes past its colour map in i_gpix_p and i_glin_p. The palette is allocated uninitialised, and only the entries a reader adds count as populated. The TGA reader stores pixel indexes without checking them against the colour map. i_gpix_p() rejects only an index greater than the count, so an index equal to it reads the first unpopulated entry, and getpixel() returns it. i_glin_p() skips any index at or beyond the count without writing that pixel to the caller's buffer. The palette-to-RGB conversion reads each row through an uninitialised buffer, so those pixels of the converted image hold prior heap contents. Reading an attacker-supplied image through Imager->read() and then fetching its pixels or converting it to RGB discloses process heap memory.
Policy evasion in Zscaler Internet Access File Type Control can allow a file to be improperly evaluated or attributed, potentially bypassing file-type enforcement in rare circumstances. The issue affects organizations using ZIA with File Type Control actively enforcing policies and requires a malicious file transfer through the ZIA tenant, low privileges (PR:L), and user interaction (UI:R). Impact is limited to low confidentiality/integrity policy-control evasion with no availability impact or code execution; no public exploit identified at time of analysis, and vendor-managed remediation is applied centrally by Zscaler.
Name-constraint bypass in rustls-webpki versions 0.101.0 through 0.103.11 and 0.104.0-alpha.1 through 0.104.0-alpha.5 allows a misissued wildcard certificate to escape permitted-subtree DNS name constraints, potentially permitting names outside the intended subtree. The flaw is reachable only after signature verification succeeds and requires a misissued wildcard certificate from a name-constrained CA, making real-world exploitation narrow and high-complexity (assessed CVSS 3.1 base 2.1, PR:N, AC:H). No public exploit identified at time of analysis; vendor-released patches are available in 0.103.12 and 0.104.0-alpha.6.
rustls-webpki 0.101.0 through 0.103.11 and 0.104.0-alpha releases before 0.104.0-alpha.6 accept X.509 name constraints that apply to URI names instead of enforcing them, so a misissued certificate that violates such a constraint is treated as valid. Impact is deliberately narrow: URI name constraints are only reachable after successful signature verification, the library provides no API for asserting URI names, and exploitation therefore requires a certificate authority in the trusted path to have misissued a certificate. There is no public exploit identified at time of analysis, no CISA KEV listing, and our assessment treats this as a low-priority, defense-in-depth hardening fix consistent with the vendor's CVSS 4.0 score of 2.1 rather than an urgent vulnerability.
Arbitrary file read in NetBackup Flex OS (versions before 6.4) lets an authenticated user who can reach the appliance's management shell read files outside the intended scope - including sensitive system configuration and credential material - by supplying a specially crafted path argument to a diagnostic command. The issue carries a CVSS 4.0 base score of 4.8 and is classified as CWE-347 (improper verification of cryptographic signature), with the advisory's associated tags pointing to an information-disclosure / JWT-style attack path. Exploitation requires valid management-shell credentials and local access to the appliance, so it is not reachable over the network without an existing account; no public exploit code has been identified at time of analysis, the CVE is not listed in CISA KEV, and vendor patches are available.
A signed/unsigned type mismatch in Netty's Memcache binary protocol codec desynchronizes frame boundaries, allowing an unauthenticated, network-positioned attacker to smuggle responses across a shared or proxied memcache connection (CVSS 3.1 base 6.5, Medium). The flaw is reachable only when the Memcache binary codec is explicitly wired into a network-exposed Netty pipeline - a non-default configuration - and the affected code ships inside Red Hat Fuse 7, JBoss Enterprise Application Platform 7, Single Sign-On 7, and the Red Hat Build of Apache Camel for Spring Boot 4. No public exploit code has been identified at time of analysis, and there is no confirmation of active exploitation (not in CISA KEV); impact is limited to confidentiality and integrity (C:L/I:L) with no availability effect.
Information disclosure in Synology DiskStation Manager (DSM) lets unauthenticated remote attackers read a limited set of files by overwhelming the built-in Auto Block brute-force protection with sustained authentication attempts. The root cause is an improper restriction of excessive authentication attempts (CWE-307), and exploitation is technically difficult (CVSS 3.7, AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N) with the payoff confined to low-confidentiality reads and no write or denial-of-service capability. Affected versions are DSM before 7.2.1-69057-10, 7.2.2-72806-7, and 7.3.2-86009-2; no public exploit identified at time of analysis, and this remains a low-priority finding despite being remotely reachable and unauthenticated.
Unauthenticated remote attackers can query the Desktop API in Synology DiskStation Manager (DSM) to retrieve non-sensitive information, affecting DSM versions before 7.2.1-69057-10, 7.2.2-72806-7, and 7.3.2-86009-2. The CVSS 3.1 score is 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N), and while no public exploit code or active exploitation has been identified at time of analysis, the flaw still offers reconnaissance value because no authentication or user interaction is required. Given the limited confidentiality impact and lack of integrity or availability effects, this is a low-priority issue, with risk primarily determined by whether the DSM management interface is internet-facing.
Information disclosure in Synology DiskStation Manager (DSM) allows remote authenticated users to obtain sensitive information by directly requesting the Wallpaper Path resource, bypassing intended navigation controls. Affected versions are DSM before 7.2.1-69057-10, 7.2.2-72806-7, and 7.3.2-86009-2. Exploitation requires a valid DSM account (PR:L) and network access to the DSM web interface; no public exploit identified at time of analysis. Vendor patches are available in the listed fixed builds.
HCL BigFix Service Management exposes internal IP addresses through its own HTTP responses - response headers, error messages, or rendered page content - allowing anyone able to reach the instance to harvest RFC1918 addressing and infer the internal network topology behind it. The consequence is reconnaissance only: no data modification, no service disruption, and a low vendor base score of 3.1, making this a low-priority item rather than an urgent one. No public exploit code was identified at time of analysis and there is no KEV or EPSS signal in the supplied data. The vendor vector specifies PR:L (a valid session) while the description claims an unauthenticated attacker, so authentication requirements are not confirmed from available data; the vendor's AC:H also implies an additional non-trivial condition or timing is needed to elicit the leak.
Improper encoding and escaping of output in the Auth API of Synology DiskStation Manager (DSM) lets remote, unauthenticated attackers retrieve information the vendor classifies as non-sensitive, affecting deployments before 7.2.1-69057-12, 7.2.2-72806-9, 7.3.2-86009-4, and 7.4-90075. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, 5.3) confirms exploitation needs no credentials, no user interaction, and no non-default configuration, so the only meaningful barrier is impact rather than access. There is no public exploit identified at time of analysis and no KEV listing, and because disclosure is limited to non-sensitive information, the practical value to an attacker is reconnaissance and fingerprinting rather than direct compromise; vendor-released patches exist in the fixed DSM builds published under Synology advisory SA_26_13.
Plaintext third-party AI provider API keys can be extracted from any WordPress site running the GPTranslate - Multilingual AI Translation Agent plugin at version 2.34.6 or earlier, because the plugin emits the stored credential into a public front-end JavaScript asset loaded by enqueue_frontend_scripts. The exposure is unauthenticated and requires no user interaction - an attacker only needs to fetch any public page and apply the inverse transformation that is itself bundled in the plugin's own public JavaScript to recover the key in cleartext (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, 5.3 Medium as published; our assessment raises the confidentiality component to High given that a raw billing-capable credential is disclosed, yielding 7.5). Keys for OpenAI, DeepL, xAI/Grok, Gemini, Claude, and Google Cloud Translation are all affected, and the default configuration (gpt-3.5-turbo in client mode) is vulnerable; only deepseek-* models and gpt-* models running in server-proxy mode correctly suppress key emission. No public exploit code was identified at time of analysis and the vulnerability is not listed in CISA KEV, though the recovery technique is trivially derivable from the plugin's own shipped assets, so treat exploitation as plausible and rotate credentials.
Unauthenticated visitors can strip the login- and URL-hiding protection from WordPress sites running the Hide My WP Ghost plugin before 7.0.11 by triggering the plugin's own loopback security-check request with a missing or incorrect verification value, causing the concealment to fail open and re-exposing the hidden WordPress login page location. The flaw is network-reachable, low complexity, and requires no authentication or user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, base 5.3), but its impact is deliberately narrow: it only reverts the site to its ordinary, unhidden login posture and does not bypass WordPress authentication, so real-world risk depends on the strength of the underlying credentials and any additional login protections in place. Publicly available exploit code exists and the issue is tracked by WPScan as well as ENISA EUVD-2026-82686; a vendor fix is available in version 7.0.11, and there is no indication of confirmed active exploitation (no CISA KEV listing) and no EPSS score was provided in the source data.
Unauthenticated attackers can strip the hardening protections from the Hide My WP Ghost WordPress plugin (versions before 7.0.11) by supplying a single WooCommerce-looking request parameter, which the plugin accepts as proof of a legitimate WooCommerce request and uses to switch off its firewall, threat detection and login/URL-hiding logic - re-exposing the concealed login and admin URLs on any request. The issue affects default installations where the plugin's protection features are enabled (its core purpose), requires no authentication, user interaction or non-default configuration (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, 5.3), and publicly available exploit code exists, with no confirmed active exploitation reported. The impact is indirect - WordPress core authentication is not bypassed - but any site treating this plugin as a meaningful obscurity control effectively loses that protection until it is upgraded to 7.0.11 or later.
Web cache poisoning in the Breeze Cache WordPress plugin before 2.5.15 allows unauthenticated remote attackers to append tracking-related query parameters that the plugin still caches responses for but omits from the page-cache key, causing a page rendered in the attacker's own request context to be stored under the clean URL's cache entry and served to every subsequent visitor. Exploitation requires only that page caching be active in its default configuration - no authentication, no user interaction, and no special setup (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N, 6.5) - and publicly available exploit code exists; the issue is not confirmed as actively exploited (not in CISA KEV). Impact is bounded to low confidentiality and integrity effects, exposing one visitor's rendered context to others and altering cached page content until the entry expires or is purged.
Missing authorization on an appointment-retrieval action in the Bookit - Booking & Appointment Calendar WordPress plugin before 2.6.0.5 lets an authenticated user holding a low-privilege Bookit-specific role pull other customers' appointment records, including names, email addresses, phone numbers and private booking comments. The underlying issue is a CWE-200 information-exposure pattern: the action returns booking PII without verifying that the caller owns the appointment or holds the capability that normally gates such data. Publicly available exploit code exists and WPScan published the finding, but there is no indication of active exploitation, impact is confined to confidentiality with no write or availability effect, and a vendor fix is available in 2.6.0.5 - making this a low-to-moderate priority disclosure issue rather than a high-severity threat.
King Addons for Elementor versions before 51.1.81 fail to enforce capability, post-status, or password checks when rendering the content of a requested post, allowing any authenticated user with Contributor-level access or higher to read the contents of private, draft, pending, and password-protected posts they are not authorized to view. The flaw is an authenticated information-disclosure issue (CWE-200) that requires only an active contributor-level account on a site running the affected plugin plus the choice of a target post ID; it grants no write, modification, or destructive capability. Publicly available exploit code exists, but there is no indication of confirmed active exploitation and the vendor has shipped a fix in 51.1.81; our independent assessment rates this a genuinely low-priority, though real and patch-worthy, authorization flaw (assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N).
An out-of-bounds read in GPAC's RTP depacketizer lets unauthenticated remote attackers crash or partially disclose memory by delivering a crafted 3GPP timed-text (TTXT) RTP payload with an oversized advertised length. The flaw lives in gf_rtp_parse_ttxt() in src/ietf/rtp_depacketizer.c and affects GPAC 26.08-DEV and earlier builds prior to abi-16.26; exploitation requires the target to be acting as an RTP receiver/depacketizer rather than simply parsing a local file. No public exploit code was identified at time of analysis and there is no confirmed active exploitation (CISA KEV), so this is a genuine but moderate-severity memory-safety defect whose practical reach depends on GPAC being deployed in an RTP-consuming configuration.
Rendering a crafted PDF with Freedesktop Poppler 26.07.0 can trigger a signed integer overflow in the TrueType font handler FoFiTrueType::mapCodeToGID when an embedded font supplies a manipulated segCnt value, producing a crash or a bounded out-of-bounds read rather than confirmed code execution. The flaw is remotely reachable with no authentication (CVSS 4.0 PR:N, CVSS 3.1 PR:N) but requires the victim or an automated pipeline to open or convert the attacker-supplied document (UI:P/UI:R), so it is not a hands-off network exploit; publicly available exploit code exists but there is no indication of confirmed active exploitation (no CISA KEV listing). With a base score of 5.3 and C:L/I:L/A:L on the assessed 3.1 vector, this is a moderate, opportunistic-risk issue rather than a top-tier priority, and it matters most to environments that automatically render or convert untrusted PDFs at scale.
NUUO Network Video Recorder 2.0.0 is vulnerable to arbitrary file read. In up.php, the url parameter submitted by the user via POST is received, and fopen() is used to open the URL in binary read-only mode. The content is then written to the /tmp/ directory, with the filename derived from basename() of the URL. This operation requires no authentication.
Imager versions from 0.45_02 before 1.035 for Perl read outside the EXIF block via unchecked start offsets in tiff_load_ifd. tiff_load_ifd() validates an IFD entry's data by checking that `entry->offset + entry->size` stays within the EXIF block, and never checks the start offset itself. Where that sum is not the real end of the data, the check passes with the entry starting outside the block. Through 1.032 `entry->offset` is a plain int, so on the usual two's-complement implementations an offset with the high bit set converts to negative and the sum can land back inside the block. From 1.033 the field is a size_t and the addition wraps only where size_t is 32 bits. The IFD's own start offset is checked the same way and wraps where unsigned long is 32 bits, which includes 64-bit Windows. Any caller of Imager->read() on an attacker-supplied image may receive EXIF tags holding bytes from outside the block, or crash the process.
Heap out-of-bounds read in the PoDoFo C++ PDF library (versions 1.0.0 through 1.1.0) lets a crafted PDF containing an Indexed color-space image cause the library to read past the end of its palette lookup buffer. An attacker must convince a victim to hand the malicious PDF to an application built on the affected library and have that application decode or render the embedded Indexed image; no authentication is required (CVSS 4.0 vector PR:N, AV:L, UI:P), and the practical impact is dominated by a process crash leading to denial of service, with only adjacent heap bytes potentially disclosed rather than targeted secret exfiltration. Exploitation yields a limited confidentiality gain and a high availability impact; no public exploit code has been identified at time of analysis and there is no CISA KEV entry. The flaw is fixed in PoDoFo 1.1.1.
Cross-origin information disclosure in Google Chrome (through the bundled Skia graphics library) affects versions prior to 153.0.8010.52, where improper state validation lets a crafted HTML page cause the renderer to expose data belonging to another origin. Exploitation requires the victim to load an attacker-controlled page (UI:R) and yields only partial confidentiality impact - no code execution, data modification, or denial of service - which is why the CVSS base score is a modest 4.3. No public exploit code has been identified at time of analysis, CISA SSVC rates exploitation as none and automatable as no, and the vendor has released a fixed build, so this should be treated as a low-priority, patch-routinely item rather than an emergency.
UI spoofing in Google Chrome's WebAppInstalls component (versions prior to 153.0.8010.52) lets a remote, unauthenticated attacker misrepresent interface elements to a user who visits a crafted HTML page, but only if the victim is successfully socially engineered into trusting the falsified prompt. Exploitation requires mandatory user interaction (CVSS UI:R) and produces only a limited integrity impact - no code execution, no data exfiltration, and no availability loss - which is why Chromium rates it Low severity. No public exploit code has been identified at time of analysis, CISA SSVC records no exploitation and rates the issue non-automatable with partial technical impact, and the vendor has released a patch in Chrome 153.0.8010.52.
Information disclosure in the Paint component of Google Chrome desktop allows unauthenticated remote attackers to obtain sensitive information when a victim renders a crafted HTML page, per CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N (6.5). Exploitation is gated by mandatory user interaction (UI:R), keeping it out of the automatable category under CISA's SSVC assessment (Exploitation: none, Automatable: no, Technical Impact: partial), and no public exploit code has been identified at time of analysis. The confidentiality-only impact - no integrity or availability effect, no code execution or sandbox escape reported - makes this a genuine but modest issue rather than an urgent priority; Google has released a fixed build, so exposure ends once Chrome is updated to 153.0.8010.52 or later.
Cross-origin information disclosure in Google Chrome's Permissions implementation allows a remote attacker to leak data across origin boundaries when a victim opens a crafted HTML page in Chrome versions prior to 153.0.8010.52. Exploitation requires user interaction (the victim must load the page) but no authentication or special privileges, and the impact is limited to low-sensitivity data exposure (CVSS 4.3, Chromium severity Medium). No public exploit code or confirmed active exploitation was identified at time of analysis, and the auto-updating Stable channel sharply narrows the exposure window once 153.0.8010.52 propagates.
Memory disclosure in Google Chrome prior to 153.0.8010.52 allows a local attacker to read out-of-bounds data through the browser's DataTransfer implementation, with the sandbox-crossing scope change (S:C) in the CVSS vector indicating the leaked memory can originate outside the renderer process rather than from within the attacker's own context. Per the assessed vector (AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N, base 6.3) exploitation requires the attacker to already be running a local program on the victim's machine and to use social engineering to obtain user interaction, and it produces only confidentiality impact with no integrity or availability effect, so this is an information-disclosure bug rather than a sandbox escape or code-execution primitive. There is no public exploit code identified at time of analysis and the issue is not confirmed actively exploited (it is not in CISA KEV); Google has shipped version 153.0.8010.52, which resolves the flaw.
Uninitialized heap memory disclosure in OpenSlide occurs because libtiff 4.7.1 changed how the indirect TIFF tile read path handles a partial bottom tile row, causing _openslide_tiff_read_tile() to request a full tile-height destination and pull uninitialized heap bytes into pixel data returned by openslide_read_region(). Only OpenSlide 4.0.0.10 and 4.0.0.11 official binary builds - or any OpenSlide build linked against libtiff 4.7.1 or newer - are affected, and exploitation requires a network service that renders attacker-supplied, non-NDPI TIFF-based whole-slide images; OpenSlide linked against libtiff 4.7.0 or earlier is explicitly not affected, and reliability of any actual data extraction depends on downstream pixel transparency handling and recompression, so the practical leak is limited and uncertain. No public exploit code was identified at time of analysis, and the issue is fixed in OpenSlide 4.0.1 and official binary build 4.0.0.12.