Information Disclosure

The API endpoint exposed by HPE Networking EdgeConnect SD-WAN Gateways can be queried by an unauthenticated remote attacker in a way that returns sensitive information, with successful exploitation yielding data that could be reused to reach other network services. Affected firmware spans the 9.4.x, 9.5.x, 9.6.x and 9.7.0.0 branches, and exploitation is rated high complexity (AC:H) even though no authentication is required. There is no public exploit code identified at time of analysis and the issue is not listed in CISA KEV, so this is currently a targeted-risk disclosure bug rather than a mass-exploitation event.

Unauthenticated remote denial-of-service in HPE Networking EdgeConnect SD-WAN Gateways lets an attacker who can reach the appliance's exposed services interrupt normal operation and take the gateway's services offline, disrupting WAN connectivity for dependent sites. Affected branches are 9.4.0.0–9.4.8.2, 9.5.0.0–9.5.8.1, 9.6.0.0–9.6.3.1 and 9.7.0.0, reported by HPE's own security-alert address. CVSS is 5.9 with a high attack-complexity qualifier and availability-only impact, and no public exploit code or confirmed active exploitation was identified at time of analysis.

EdgeConnect SD-WAN Gateways expose sensitive information to any user who can authenticate to the web-based management interface with low privileges, letting them read data that can be reused to reach other network services managed by the gateway. All four supported branches listed by ENISA (9.4.0.0-9.4.8.2, 9.5.0.0-9.5.8.1, 9.6.0.0-9.6.3.1, and 9.7.0.0) are affected, per HPE's advisory hpesbnw05135en_us. The flaw is rated 6.5 (network vector, low privileges, no user interaction, confidentiality-only impact); no public exploit code and no CISA KEV listing were identified at time of analysis, so exploitation currently depends on an attacker already holding valid low-privilege credentials and reachability to the management interface.

DigestAuth replay protection in http4s mishandles the nonce-count it stores, so the server's counter can lag behind the highest value it has actually accepted; a passive network observer who captures one legitimate Digest Authorization header can therefore replay it repeatedly before the counter catches up. Successful replays are executed as the captured user and include state-changing requests, defeating the replay resistance that Digest authentication is supposed to provide over Basic auth. Only applications that explicitly mount the DigestAuth middleware are affected, versions 0.23.x before 0.23.35 and 1.0.0 milestones M1 through M46 are impacted, and the flaw is fixed in 0.23.35 and 1.0.0-M47. No public exploit code or active exploitation has been identified at time of analysis.

Improper certificate validation in the shared HTTP client used by Devolutions Server 2026.2.16 and earlier synchronization and integration features allows a network-positioned attacker to intercept and tamper with outbound TLS connections by presenting a spoofed or self-signed certificate. The flaw is unauthenticated (PR:N) with no user interaction required, but exploitation demands both the sync/integration feature to be configured and actively making outbound connections, and the attacker to already hold a man-in-the-middle position on that network path, which is why the assessed vector carries AC:H and the impact is limited to partial confidentiality and integrity loss (C:L/I:L) on outbound integration traffic only. No public exploit code has been identified at time of analysis, there is no CISA KEV entry, and the EPSS score is 0.09% (1st percentile), so this is a genuine but low-to-medium priority issue that should be remediated through normal patch cycles rather than emergency response.

Order access tokens in the J2Store/J2Commerce extension for Joomla (versions 1.0.0-3.3.2, 4.0.0-4.0.22, and 4.1.0-4.1.7) are derived predictably, so anyone who already knows the site's Joomla `secret` value can compute a valid token for any order on the store. This grants guest-level access to that order's details and any purchased digital downloads without the attacker ever placing an order. The token is never rotated, so the exposure survives even after the original secret-disclosure bug is patched unless the Joomla `secret` itself is changed. No public exploit tooling is identified at time of analysis, and the issue is not listed as confirmed actively exploited (CISA KEV); exploitation is non-trivial because it presumes a prior foothold or disclosure of the site secret (CVSS 4.0 AC:H).

The CookieJar client middleware in http4s before 0.23.35 and 1.0.0-M47 stores a response cookie's Domain attribute without verifying that it domain-matches the host that set it, so any malicious or compromised server reached through the same cookie jar can plant a cookie addressed to an unrelated victim domain. When the client later talks to that victim domain, the jar replays the attacker-controlled cookie, enabling session fixation or overwriting of security-sensitive cookies; the flaw has CVSS 6.8 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N) with no public exploit code identified at time of analysis, and fixes land in 0.23.35 and 1.0.0-M47.

The FollowRedirect client middleware in http4s strips Authorization and Cookie headers only when a redirect crosses to a different authority, ignoring URI scheme changes; a same-host redirect from HTTPS to HTTP therefore re-sends credentials in cleartext over the network. Applications using http4s client versions prior to 0.23.35 or 1.0.0-M47 and following attacker-influenced redirects can leak bearer tokens, basic-auth credentials, and session cookies to anyone able to observe the plaintext connection. The flaw is fixed in 0.23.35 and 1.0.0-M47; no public exploit code or CISA KEV entry was identified at time of analysis, and exploitation requires the attacker to influence a redirect target and sit on the network path.

Authenticated users with editor-level or higher privileges in Concrete CMS 9.x before 9.5.3 can degrade site availability by submitting keyword searches packed with SQL LIKE wildcard characters, which the application failed to escape before placing them into the LIKE clause. Because a single-character wildcard matches any row, a short request forces the database into full-table scans, and repeated or wildcard-dense searches can sustain elevated database CPU and I/O on large installations, slowing the site for all users. The Concrete CMS security team rated this CVSS v4.0 2.1 (availability-only, attack requirements present, high privileges); no public exploit code has been identified at time of analysis.

Http4s client applications that keep a cookie jar can leak stored cookies — including session and authentication cookies — to attacker-controlled hosts because versions prior to 0.23.35 and 1.0.0-M47 decide cookie applicability with unanchored substring checks instead of RFC 6265 domain and path matching. A cookie scoped to example.com is therefore also attached to requests for evilexample.com, api.example.com.attacker.net, or an unrelated path, so any attacker who can influence the outbound URL the application requests receives the cookie and can hijack that outbound session. The flaw is fixed in 0.23.35 and 1.0.0-M47; no public exploit code and no CISA KEV entry were identified at time of analysis.

Affected versions of Arista EOS can write plaintext TACACS+ shared secrets into a location an operator can read, exposing the secret that protects authentication traffic between the switch and its AAA servers. Exploitation is not remote: it requires a highly privileged local session (CVSS PR:H), a non-default/specific set of circumstances (AC:H), and a user action (UI:R), which is why the score sits at 6.3 despite high confidentiality, integrity, and availability metrics. There is no public exploit code identified and the issue is not listed in CISA KEV, so this is a hardening/credential-hygiene issue rather than an actively attacked one; note that a leaked TACACS+ secret is high-value for lateral movement across network infrastructure.

Cleartext user passwords can be written into Arista EOS log files when specialized, non-standard debugging trace levels are explicitly enabled on the device. Only operators who already hold authenticated local administrative shell access and who have turned on these unusual trace levels are exposed, and a user must actually authenticate while tracing is active for credentials to be recorded. Arista discovered the flaw internally, states it is not aware of any malicious exploitation, and no public exploit code or CISA KEV entry has been identified; vendor advisory SA-0153 documents the fix

Arista EOS switches can write plaintext private keys into log files when specialized, non-standard debugging trace levels are explicitly enabled on the device. Exploitation requires an attacker to already hold authenticated local administrative access to the device shell and to have those special debug trace levels turned on, so the practical exposure is primarily insider or post-compromise rather than remote. Arista discovered the flaw internally (SA-0153), states it is unaware of malicious exploitation in customer networks, and the issue is not listed in CISA KEV and no public exploit code has been identified.

An out-of-bounds read in the Pixel-specific physmem_extmem driver (physmem_extmem_linux.c) of the Android kernel lets a local process with low privileges read kernel memory that was never initialized, exposing potentially sensitive data. No user interaction or elevated execution privileges are required, and the impact is limited to confidentiality (CVSS 5.5, AV:L/PR:L/C:H). The issue is addressed in the September 2026 Android/Pixel security bulletin; no public exploit code or CISA KEV listing was identified at the time of analysis.

Uninitialized memory use in multiple locations of the Android kernel allows a locally-positioned attacker who already holds System-level execution privileges to read stale kernel memory contents, resulting in information disclosure. The flaw is rated CVSS 4.4 (AV:L/PR:H) and affects Android builds covered by the September 2026 Pixel/Android Security Bulletin; user interaction is not required. No public exploit code and no CISA KEV listing were identified at time of analysis, and the exploitation prerequisite of pre-existing System privileges keeps the practical risk confined to post-compromise or privileged-local scenarios.

A logic error in the Android kernel's ACFW FF-A (Firmware Framework for Arm A-profile) driver, implemented in acfw_ffa.c, allows a caller already holding System-level execution privileges to read memory that should remain secret, resulting in local information disclosure. Exploitation requires local access and high privileges, needs no user interaction, and affects Android devices carrying the affected kernel build per Google's Pixel security bulletin for September 2026. No public exploit code or active exploitation has been identified at time of analysis, and the CVSS 3.1 base score of 4.4 reflects limited confidentiality impact confined to already-privileged local actors.

An out-of-bounds read in the Android kernel driver routine gf_algo_get_cached_dump_data (gf_algo.c) lets a locally positioned attacker with limited privileges read past the end of a buffer and leak kernel memory contents, with no user interaction required. Pixel builds that ship the vulnerable gf_ driver are affected, and the September 2026 Android/Pixel security bulletin provides the fix. Neither public exploit code nor a CISA KEV entry was present in the supplied intelligence, and no EPSS score was provided, so active exploitation is unconfirmed and the practical threat at time of analysis is a local, post-compromise or malicious-app information leak.

Improper input validation in the MBU class handler (validate_ns_buf in mbu_class.rs) of the Android kernel allows a component already running with System execution privileges to supply a malformed namespace buffer and read kernel memory beyond the intended bounds, disclosing sensitive data. Affected are Android devices built on the impacted kernel (CPE cpe:2.3:a:google:android) as addressed by the September 2026 Android/Pixel security bulletin. The CVSS 3.1 score of 4.4 is intentionally modest because exploitation demands local code execution at a high privilege level (PR:H) with no user interaction; no public exploit code has been identified and no EPSS score was supplied with this record.

An out-of-bounds read in ReadDataElement (common.c) within the Android platform allows a locally installed application to disclose sensitive memory contents without any additional execution privileges or user interaction. The flaw is a missing/incorrect bounds check on an attacker-influenced length or index value, rated CVSS 5.5 (AV:L/AC:L/PR:L/UI:N, C:H/I:N/A:N), so the practical impact is confidentiality loss rather than code execution. Affected builds are Android platform components referenced by the September 2026 Pixel/Android security bulletin; no public exploit code or CISA KEV listing was identified at time of analysis, and the EPSS signal is absent from the supplied data.

A permission bypass in Google Android stemming from a side-channel information disclosure (CWE-203) allows a local attacker holding only low-privileged code execution to escalate privileges without any user interaction. The flaw yields high confidentiality impact (CVSS 5.5, AV:L/AC:L/PR:L/UI:N) by leaking observable discrepancies that undermine permission enforcement, though the vendor vector records no integrity or availability impact. It is addressed in the September 2026 Android/Pixel security bulletin; no public exploit code or CISA KEV listing was identified in the supplied intelligence at time of analysis.

A logic error in the Android kernel's VPU (Video Processing Unit) driver can disclose kernel memory contents to code that is already running with System-level privileges. The flaw is local-only: CVSS gives AV:L with PR:H, so an attacker must first obtain elevated (System) execution on the device before triggering the information leak, and no user interaction is required once that precondition is met. There is no public exploit code and no CISA KEV listing at time of analysis, and the associated EPSS data was not supplied, so this should be treated as a post-compromise information-disclosure primitive rather than a remotely exploitable issue.

Local information disclosure in Google Android's CPM component allows a caller holding System-level execution privileges to read protected data by abusing a confused deputy (CWE-441) that performs an action on behalf of a less privileged requester without re-validating the caller's authority. Only locally positioned code already running with System privileges on an affected Android build can trigger the flaw, and no user interaction is required. There is no CISA KEV listing and no public exploit code identified at time of analysis, so the practical risk is limited to post-compromise or privileged-app scenarios rather than remote attack.

An out-of-bounds read in the AES-GCM-256 crypto implementation of the Android kernel (function do_sss_aes_gcm_256_op in crypto-aes.c) allows disclosure of memory contents to code that is already running at System privilege on an affected device. The flaw is a missing bounds check on an input length or index (CWE-120 class buffer handling error), rated 4.4 (Medium) with the vector CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N, meaning exploitation is local and requires the attacker to already hold System (PR:H) execution privileges; no user interaction is needed once that position is held. There is no indication of confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis, and because the entry point sits behind a high privilege boundary the practical risk is a post-compromise or chained privilege-escalation information leak rather than an independent remote threat.

Arista EOS devices with password-based authentication enabled can accumulate orphan authentication sessions when a specially crafted password string is submitted to the management login path. Repeatedly sending such passwords exhausts the device's authentication resources, so legitimate administrators are locked out of the switch. Arista discovered the flaw internally and states it has no evidence of malicious exploitation in customer networks; no public exploit code or CISA KEV listing was identified in the supplied intelligence. The vendor-rated CVSS 4.0 score is 6.9 with availability-only impact.

Ingress Security ACLs applied to Switched Virtual Interfaces (SVIs) in shared mode on dual-switchcard Arista EOS platforms can silently stop filtering after the secondary switchcard forwarding agent restarts or a secondary switchcard is inserted, causing packets that should be denied to be permitted (and vice versa). The flaw is rated CVSS 4.8 (AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N, CWE-1419 incorrect resource initialization) and only affects modular chassis configured with dual switch cards plus shared-mode SVI ingress ACLs. Arista discovered the issue internally and states it is not aware of any malicious exploitation in customer networks; no public exploit code or CISA KEV listing is associated with this CVE.

Improper authorization checks on GitLab CE/EE internal data emission endpoints let an authenticated user retrieve sensitive credentials and tokens that should only have been returned along the expected proxy path. All releases from 10.1.0 before 19.1.8, the 19.2 branch before 19.2.6, and the 19.3 branch before 19.3.2 are affected according to the vendor, and publicly available exploit code exists (HackerOne report 3907835). Impact is confidentiality-only (CVSS 5.3, C:L/I:N/A:N), with no CISA KEV listing and no EPSS score supplied in the source data.

An XPath injection flaw (CWE-643) in IBM Cloud Pak for Business Automation lets an authenticated user manipulate XPath queries and read data the query engine should never return, including sensitive application records and structural details of the underlying XML documents. All shipped 24.0.x, 25.0.0 and 26.0.0 streams are affected up to and including Interim Fix 001/005/008/009 respectively, and exploitation only requires a low-privileged, network-reachable session — no user interaction and no special complexity. IBM has published a vendor fix; there is no CISA KEV listing and no public exploit code identified at time of analysis, so this is currently a patch-on-schedule issue rather than an emergency.

A path-handling flaw in the containers/storage Go library lets a crafted tar archive containing a malicious whiteout entry (for example 'victim/.wh.') cause UnpackLayer, ApplyLayer, or ApplyUncompressedLayer to replace the extraction destination directory with an arbitrary file. Systems that unpack container image layers with this library — notably Red Hat Enterprise Linux 10, Red Hat Ansible Automation Platform 2, OpenShift Container Platform 4, Quay 3, OpenShift Virtualization, Dev Spaces, and Red Hat Hardened Images — are in scope. Exploitation requires the operator or process to unpack an attacker-supplied archive, and the integrity impact is confined to the local extraction target; no public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV, consistent with the modest CVSS 3.1 base score of 4.4.

Vikunja releases before 2.6.0 return the raw TOTP shared secret from the GET /api/v1/user/settings/totp and /api/v1/user/settings/totp/qrcode endpoints without demanding re-authentication, so anyone holding a valid access token can clone the victim's second factor. Because the exposed seed lets an attacker generate valid codes indefinitely, a hijacked session token can be converted into durable account takeover that survives password changes but not TOTP secret rotation. The vendor has shipped a fix in 2.6.0; no public exploit code or CISA KEV entry was identified at time of analysis.

Missing authorization checks in Vikunja's v2 API allow anyone holding a read-only project link-share token to enumerate users through the project users endpoint and to confirm arbitrary usernames exist via the global search endpoint. All Vikunja deployments before 2.6.0 are affected; the flaw is a limited-confidentiality information disclosure (CVSS 4.3, PR:L because a share token is required) and is fixed in 2.6.0. No public exploit code or CISA KEV entry was present at time of analysis.

Vikunja versions before 2.6.0 omit team-level access validation when a team is attached to a project, letting any authenticated user enumerate teams they do not belong to through the project teams endpoint. An attacker with a low-privileged account can supply arbitrary team IDs and receive complete rosters - member names and administrative flags - for unauthorized teams. Impact is confidential-only (CVSS 4.3, CWE-200) and no public exploit code or KEV listing was provided with the source data.

Opening a crafted .rdp connection file in the FreeRDP xfreerdp X11 client (versions 3.11.0 through 3.30.0) can trigger out-of-bounds heap reads and writes because the client fails to validate MonitorIds array values in xf_detect_monitors. This local, user-interaction-gated flaw requires a victim to open the malicious file and does not affect the RDP server side; publicly available exploit code exists, but there is no confirmation of active exploitation (not in CISA KEV). The vendor has released a patch in FreeRDP 3.31.0, and the CVSS 6.9 rating reflects limited confidentiality and integrity impact with a high availability impact.

Incomplete comparison logic in OpenClaw ClawScan's built-in static scanner (internal/runner/static_scanner.go) through version 0.1.6 lets packaged Python bytecode slip past the deterministic text scan, so malicious skills or OpenClaw plugins can pass inspection undetected. The vendor fix in v0.1.7 (commit 9f6a6fbb9f1137345566d0ab44c73893dfe112fa, PR #41) explicitly adds flagging of packaged Python bytecode as opaque executable content. A publicly available exploit (GitHub issue #40) demonstrates the bypass, but the flaw is local-only, requires a low-privileged local user plus passive user interaction, and yields only a low integrity impact (CVSS 4.0 base 0.9).

ClawScan 0.1.6 and earlier misclassifies NUL-obfuscated or otherwise ambiguous files as opaque binary content, so its built-in static scanner skips them and malicious OpenClaw skill or plugin code passes inspection undetected. Exploitation requires local access and the victim to run or act on a ClawScan report, giving the attacker a way to smuggle hostile code past the only automated gate. Public exploit code exists (GitHub issue #42), and the defect is resolved in 0.1.7 via commit 04401337b3adb9343bd338b21e5e258bf49ca9c8; CVSS 4.0 base score is 2.4, reflecting the limited integrity-only, local impact.

Payara Server ships by default without any cap on failed authentication attempts, so its administrative console and application login endpoints can be hammered with unlimited password guesses. The issue is a classic missing-lockout / missing-rate-limit weakness (CWE-307) affecting Payara Server Enterprise 4.x, 5.x, 6.x and 7.x plus the Payara Server Community 7 line, with fixes published in releases 4.1.2.191.57, 5.89.0, 6.40.0, 7.2.0 and Community 7.2026.7. With a vendor CVSS of 6.3 (4.0 vector AV:A/AC:L/PR:N/UI:N, VC:L/SC:H), success depends on the operator enabling the bundled automatic attack protection; no public exploit code or CISA KEV listing was present in the supplied intelligence, and no EPSS score was provided.

Incorrect boundary conditions in the Networking component. This vulnerability was fixed in Firefox 156 and Firefox ESR 153.3.

Incorrect boundary conditions in the Safe Browsing component. This vulnerability was fixed in Firefox 156 and Firefox ESR 153.3.

Sandbox escape due to incorrect boundary conditions in the Widget: Win32 component. This vulnerability was fixed in Firefox 156 and Firefox ESR 153.3.

Information disclosure in the Networking component. This vulnerability was fixed in Firefox 156 and Firefox ESR 153.3.

Spoofing issue in the DOM: Navigation component. This vulnerability was fixed in Firefox 156 and Firefox ESR 153.3.

Site isolation issue in the Reader Mode component. This vulnerability was fixed in Firefox 156 and Firefox ESR 153.3.

Sandbox escape in the Profile Backup component. This vulnerability was fixed in Firefox 156.

Sandbox escape due to incorrect boundary conditions in the Widget: Win32 component. This vulnerability was fixed in Firefox 156 and Firefox ESR 153.3.

Sandbox escape due to incorrect boundary conditions in the Widget: Win32 component. This vulnerability was fixed in Firefox 156 and Firefox ESR 153.3.

Incorrect boundary conditions in the Security: Process Sandboxing component. This vulnerability was fixed in Firefox 156.

Incorrect boundary conditions in the DOM: Editor component. This vulnerability was fixed in Firefox 156 and Firefox ESR 153.3.

Spoofing issue due to invalid pointer in the Graphics component. This vulnerability was fixed in Firefox 156.

Sandbox escape due to race condition in the XPConnect component. This vulnerability was fixed in Firefox 156.

Sandbox escape due to incorrect boundary conditions in the Widget: Win32 component. This vulnerability was fixed in Firefox 156 and Firefox ESR 153.3.

Sandbox escape due to incorrect boundary conditions in the WebRTC component. This vulnerability was fixed in Firefox 156 and Firefox ESR 153.3.

Information disclosure in the Networking: HTTP component. This vulnerability was fixed in Firefox 156 and Firefox ESR 153.3.

Incorrect boundary conditions in the DOM: Animation component. This vulnerability was fixed in Firefox 156.

Incorrect boundary conditions in the Networking: HTTP component. This vulnerability was fixed in Firefox 156.

Sandbox escape due to incorrect boundary conditions in the Graphics component. This vulnerability was fixed in Firefox 156 and Firefox ESR 153.3.

Site isolation issue in the Graphics component. This vulnerability was fixed in Firefox 156.

Sandbox escape due to invalid pointer in the Graphics component. This vulnerability was fixed in Firefox 156, Firefox ESR 140.16, and Firefox ESR 153.3.

Information disclosure in the Graphics: ImageLib component. This vulnerability was fixed in Firefox 156, Firefox ESR 140.16, and Firefox ESR 153.3.

Unauthenticated information disclosure in Evolution API through 2.3.7: an incorrect array comparison in the metricsIPWhitelist middleware always evaluates to false, so the IP allowlist check never enforces and any network attacker can reach the Prometheus /metrics endpoint. The exposed metrics leak server version, database client name, configured server URL and WhatsApp instance details, which is useful reconnaissance material for follow-on attacks against self-hosted WhatsApp gateways. Publicly available exploit code exists (VulnCheck-reported, with a linked GitHub write-up); the issue is not listed in CISA KEV and no EPSS score was provided in the input.

Failed authentication attempts against MISP 2.5.45 and earlier stop being written to the audit log whenever the Redis instance used for log throttling is unreachable, and they remain unwritten for the entire duration of the outage. The flaw is in AppController::_shouldLog(), which treats 'Redis returned false' as 'nothing to log' rather than degrading to verbose logging, so brute-force or credential-stuffing activity against the login endpoint silently disappears from the record. No public exploit code and no CISA KEV entry exist for this issue, and the vendor shipped a fix in MISP 2.5.46 via commit a39b25d2f.

GNOME Shell fails to validate the declared dimensions of icons returned by a remote search provider over D-Bus against the actual icon data buffer, producing an out-of-bounds read when an oversized size is supplied. A malicious or compromised search provider registered in a user's session can crash the shell — terminating the desktop session — and may leak fragments of adjacent shell memory. Rated CVSS 6.1 (AV:L/UI:R/C:L/A:H) by Red Hat; no public exploit code or CISA KEV entry was identified at time of analysis, so exploitation currently requires a locally present hostile search provider rather than remote access.

The mailto scheme parser added to fast-uri 4.1.3 (and still present in 4.1.4) compares query field names against the reserved names 'to', 'subject' and 'body' while they are still percent-encoded, then decodes them only when storing them as generic headers — so a percent-encoded spelling of a reserved field is invisible to that check but is written back out as the literal field name during serialization. Any application built on Fastify, ajv or similar Node.js stacks that parses a mailto URI, validates, logs or displays the recipient list, and then re-serializes it with fast-uri before sending can be tricked into delivering mail to an attacker-chosen address, with subject and body content smuggled across the same roundtrip. The flaw is rated 4.8 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N, CWE-172 Encoding Error) and is fixed in fast-uri 4.1.5.

Host allowlist and denylist bypass in fast-uri, the dependency-free RFC 3986 URI parser used by Fastify and ajv, affects releases before 2.4.7, 3.0.0 through 3.1.7, and 4.0.0 through 4.1.4. Because the library lowercases the host before percent-decoding it, an encoded uppercase octet such as %41 survives as a literal 'A', and in scheme-relative references like //host the canonicalization pass that would normally repair this never runs, so parse, normalize, and equal disagree about the same hostname. Any application that makes a case-sensitive host decision on fast-uri output — a host allowlist or denylist comparing the parsed host, or code relying on equal — can be steered past that check while the evading spelling still resolves to the gated host in DNS and HTTP. Exploitation status: no public exploit identified at time of analysis.

WSO2 Identity Server exposes a user-enumeration weakness in its SMS OTP login flow: the error messages returned when the OTP challenge is initiated differ depending on whether the supplied account exists, giving unauthenticated remote attackers a way to confirm valid usernames. The signal is strongest for accounts that have no mobile number registered, which produce a distinct response. No public exploit code or CISA KEV entry was identified at time of analysis, and the CVSS 3.1 score is only 3.7 — the practical value to an attacker is the harvested username list, which feeds later brute-force and social-engineering campaigns rather than yielding direct compromise.

The self-registration flow in WSO2 Identity Server and related WSO2 identity/API management products returns a distinct error when a submitted username already exists, letting unauthenticated users enumerate valid accounts. Any remote party who can reach the self-registration endpoint can harvest a list of confirmed usernames, which then feeds credential-stuffing, brute-force, and targeted phishing campaigns. Rated CVSS 5.3 (medium) with confidentiality-only impact; no public exploit code or active exploitation is identified in the supplied data at time of analysis.

MISP 2.5.45 and earlier can write corrupted access-log records for any HTTP request that ends in an unhandled exception, because CakePHP's CakeErrorController extends AppController and re-runs the application startup path, causing AccessLog::logRequest() to register a second deferred writer that overwrites the row written by the first pass. The overwritten fields include request duration, SQL query count, memory usage and potentially the query log, silently degrading the fidelity of MISP's own audit trail. Exploitation requires an authenticated session (CVSS 4.0 PR:L, VI:L only); no public exploit code or CISA KEV listing was identified at time of analysis, and an upstream fix commit (0dae5c072) is available.

WP Directory Kit, a WordPress directory/listing plugin, exposes the content of draft and unapproved listings to anyone who can reach its public AJAX actions. Versions through 1.5.7 omit status and ownership checks before returning listing content, so unauthenticated attackers can enumerate other users' unpublished submissions (CWE-200, information disclosure). Publicly available exploit code exists per the WPScan reference, though EPSS is only 0.14% (4th percentile) and there is no CISA KEV listing, so this is a moderate, opportunistic-targeting issue rather than a mass-exploitation event.

Missing authorization and visibility checks in a WP Directory Kit shortcode (WordPress plugin versions up to and including 1.5.7) allow any logged-in user with a role as low as Contributor to read non-public listing content — including password-protected entries and hidden fields — that belongs to other users. The flaw is an information-disclosure issue (CWE-200) publicly documented by WPScan with exploit detail available, though the EPSS score of 0.14% (4th percentile) and the absence of any CISA KEV entry indicate no confirmed active exploitation and low predicted mass-exploitation risk. Impact is confidentiality-only and limited in scope: no data modification, no denial of service, and no privilege escalation beyond the reading of restricted listing data.

ManabiPocket for Parents 1.2.3 and earlier — an Android companion app for a Japanese parental school-communication service published by NTT Docomo Business, Inc. — exposes at least one application component that is reachable by other apps on the same device. A malicious app the user has already installed can send a crafted Intent to that component and read sensitive data held by the parental app, making this a local information-disclosure issue rather than a remote compromise. Severity is low (CVSS 4.0 base 1.8) because exploitation requires local code execution, user interaction and additional attack requirements; no public exploit code and no CISA KEV entry were identified at time of analysis, and EPSS data was not supplied.

TLS private key exposure in hawtio-operator affects Red Hat Build of Apache Camel - Hawtio 4 deployments on OpenShift. When a custom Route TLS secret is configured and debug logging is set to level 1 or higher, the operator serializes the complete Route object - including the TLS private key in PEM format - to its standard output. Because operator logs are routinely aggregated into centralized logging platforms and are accessible to any principal holding pods/log access in the openshift-operators namespace, this creates a pathway for credential exfiltration without direct secret access. No public exploit code exists and this CVE is not in CISA KEV, but the low debug threshold (level 1) means the exposure is frequently triggered during normal troubleshooting workflows.

Confused deputy exploitation in hawtio-operator on OpenShift allows a namespace-scoped edit user to claim arbitrary externally-routable Route hostnames that would normally require elevated cluster permissions. The operator holds a cluster-wide `routes/custom-host:create` privilege and blindly propagates the tenant-controlled `spec.routeHostName` field from Hawtio custom resources into OpenShift Route specs without validating whether the requesting user is authorized to claim that hostname. The captured subdomain can then be combined with the cluster's auto-grant OAuthClient to hijack OAuth redirect flows and steal tokens from legitimate users (PR:L, UI:R, C:H, CVSS 6.3). No public exploit code has been identified at time of analysis.

Unauthenticated access to the `/blacklist` endpoint of Maltrail (versions up to 3.0.1) allows any remote caller to retrieve source IP addresses of events that matched the operator's BLACKLIST rules, exposing internal network hosts flagged by the threat detection system. The oversight - a missing session check on one endpoint while all sibling endpoints (`/events`, `/counts`, `/hunt`, `/meta`, `/geo`) correctly required authentication - was confirmed by the vendor and patched in version 3.1 the same day it was reported. A public proof-of-concept exploit is available, making exploitation trivially scriptable against exposed instances.

Unauthenticated information disclosure in the 3D FlipBook - PDF Embedder, PDF Flipbook Viewer, Flipbook Image Gallery WordPress plugin (all versions ≤1.16.20) allows any remote attacker to retrieve the full metadata payload of password-protected flipbooks - including title, outline, props, and the serialized data blob containing the underlying PDF file's direct URL - bypassing WordPress post-password confidentiality entirely. The plugin's AJAX handler in inc/ajax-get.php processes the 'id' parameter without verifying that the requestor has authenticated against the post password, and a companion unauthenticated AJAX action (fb3d_send_posts) enables systematic enumeration of all flipbook post IDs with no prior knowledge of the target site's content structure. No public exploit code and no CISA KEV listing exist at time of analysis.

Unauthenticated information disclosure in D-Link DIR-882 routers (firmware up to 20260814) allows remote attackers to retrieve sensitive data by sending crafted requests to the /HNAP1/dllog.cgi CGI binary endpoint. The vulnerability resides in the main() function of the dllog.cgi component, which fails to properly restrict output before returning it to the caller. A public proof-of-concept exists, per the GitHub reference, which also links this endpoint to quick VPN settings disclosure - suggesting credentials or configuration material may be exposed. No public KEV listing and no vendor patch have been identified at time of analysis.

PHPGurukul Blood Donor Management System 1.0 stores credentials in cleartext on disk when crafted values are supplied to the password, email, currentpassword, dbcurrentpwd, or newpassword arguments handled by application/models/admin/Login_Model.php. Vulnerable code paths are reachable remotely per the CVSS 4.0 vector (AV:N/PR:N/UI:N), although exploitation complexity is rated high (AC:H) and only a low confidentiality impact is scored. Publicly available exploit code exists and is flagged with an Exploit maturity of P in the CVSS vector, so the flaw should be treated as exploitable even though the base score is only 2.9 and no CISA KEV entry is present.

In BharatMLStack up to and including v1.3.0, Trufflebox UI stores the JWT authentication token, full user object, and session ID in the browser's localStorage, which is fully accessible to any JavaScript running on the page.

An issue was discovered in Keyfactor SignServer before 7.6.0. The output file to which SignerStatusReportWorker logs the report can be set to any path, even one that points to a file that already exists. This gives a user (with admin access) the possibility to write files in arbitrary directories in the server filesystem and potentially overwrite files accessible by the local user JBoss.

An issue was discovered in Keyfactor SignServer before 7.6.0. The attribute ATTRIBUTESFILE in PKCS11CryptoToken can be set to a readable file but not an accepted file (i.e., recognized with attributes). In this case, an error is thrown which - together with the error - also prints the content of the file to the application server log. This gives a user that has both SignServer admin access and access to read the output of the server log (i.e., if remote syslog shipping is configured), the possibility to read the content of files accessible by the local user JBoss.

Local file enumeration in Keyfactor SignServer before 7.6.0 allows an authenticated administrator to confirm the existence and readability of arbitrary files on the application server by pointing configurable path properties at them and observing distinguishable error responses. The three affected properties are ATTRIBUTESFILE in PKCS11CryptoToken, KEYSTOREPATH in KeyStoreCryptoToken, and TRUSTSTOREPATH in RenewalWorker. No file contents are disclosed, exploitation requires a high-privileged admin account (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N, base 2.3), and there is no public exploit identified at time of analysis; EPSS is 0.15% (5th percentile), consistent with a low-priority information-disclosure issue.

Tenda Technology Co., Ltd NVR_4H CH3 v2.1 V27.5.58.6 was discovered to contain a hardcoded cryptographic key.

SmartAdmin API Java17 SpringBoot3 version 3.30.0 contains an improper authorization vulnerability in the /employee/queryAll endpoint. The endpoint does not enforce the required function-level permission or data-scope authorization, allowing an authenticated low-privileged employee to retrieve employee records belonging to other departments and users

Insufficient data exists to characterize this vulnerability. The only available intelligence is a CVE identifier, a two-word description ('security update'), and a single vendor attribution to Ubuntu. No affected product, component, version range, vulnerability class, impact, or attack vector has been disclosed in the provided data. No independent assessment of severity, exploitability, or remediation is possible from the available information.

DocsGPT through version 0.20.0 leaks OAuth connector session tokens and provider account emails to attacker-controlled windows via an insecure postMessage implementation. The callback-status endpoint broadcasts OAuth tokens using a wildcard target origin ('*') without validating the sender's origin, allowing any page acting as window.opener during the OAuth authorization flow to intercept the message payload. An attacker who tricks a victim into initiating an OAuth cloud storage connector flow from an attacker-controlled page can steal session tokens and subsequently disconnect the victim's cloud storage connectors. No public exploit has been identified at time of analysis; EPSS data not provided.

GrowthBook through version 5.0.1 leaks raw warehouse SQL queries, schema details, table names, filter values, and datasource identifiers via unauthenticated public report and experiment endpoints. Any party who obtains a publicly shared report or experiment identifier can retrieve these internal data warehouse details without authentication. No public exploit or active exploitation has been identified, but the exposed SQL and schema intelligence can directly inform subsequent attacks against the underlying data warehouse infrastructure.

ZITADEL 4.0.0 through 4.15.3 (and EOL 3.0.0 through 3.4.12) fails to fully revoke role assignments on Project Grants when an administrator deletes two or more project roles at the same time, letting affected users keep permissions that were supposed to be removed. The flaw is an off-by-one style error (CWE-193) in the cross-organization cascade cleanup that iterates a user's role list for User Grants on Granted Projects, so one or more deletions can be skipped and, if the retained role was administrative, the user may keep elevated rights inside that shared project. Publicly available exploit code exists (a public gist referencing the issue), but there is no CISA KEV listing; vendor patch 4.16.0 ships a database migration that automatically repairs residue left in the eventstore.

A buffer overflow in a PASE (Portable Application Solutions Environment) process on IBM i 7.3, 7.4, 7.5, and 7.6 allows an authenticated local user to crash the affected process. Per IBM's own description, the impact is limited: the attacker can terminate their own process rather than disrupt other users or system-wide services, which is reflected in the low CVSS 3.3 and Availability-only impact. There is no public exploit code and no CISA KEV listing at time of analysis, and the flaw is classified as CWE-125 (out-of-bounds read).

A time-of-check to time-of-use (TOCTOU) race condition in IBM i releases 7.3, 7.4, 7.5, and 7.6 lets a local attacker win a race window during a privileged file-ownership operation and end up owning arbitrary file system objects on the system. Successful exploitation yields low-level confidentiality, integrity, and availability impact but crosses a security boundary (CVSS scope change), meaning objects outside the attacker's own authority can be reassigned. No public exploit code or CISA KEV entry was identified at time of analysis, and no EPSS score was supplied; the CVSS base score is 6.0.

Local information disclosure in Apple macOS allows a malicious application already running on the host to bypass permission validation and read restricted files. Affected versions are those prior to macOS Golden Gate 27, macOS Sequoia 15.8, and macOS Tahoe 26.7. No public exploit code has been identified, and EPSS is low (0.16%), but the flaw requires only local app execution with low privileges and no user interaction, yielding high confidentiality impact (CVSS 5.5).

An information-disclosure flaw in Apple's WebKit-based browser stack lets a malicious website infer which applications a user has installed across Safari, iOS/iPadOS, and macOS. Apple addressed it through improved state management in Safari 27, iOS 27 and iPadOS 27, and macOS Golden Gate 27, so any device still on an earlier release remains exposed. Exploitation requires the victim to visit the attacker's page (CVSS UI:R) and yields only low-confidentiality impact, with no public exploit code and no CISA KEV listing at time of analysis.

A race condition in Apple macOS kernel locking allows a local user with existing code execution on the host to read kernel memory, fixed in macOS Sequoia 15.8, macOS Tahoe 26.7, and macOS Golden Gate 27. Exploitation requires local authenticated access and a high-complexity timing win in the kernel's locking path, so it is probabilistic rather than reliable, and the impact is limited to confidentiality (kernel memory disclosure) with no code execution, modification, or denial of service. There is no public exploit identified at time of analysis, the issue is not in CISA KEV, and EPSS is low at 0.19% (8th percentile), making this a genuine but low-priority issue.

A race condition in Apple macOS state management allows a locally executing application to read sensitive user data; the flaw is fixed in macOS Golden Gate 27, and all earlier macOS versions are affected. Exploitation requires an attacker-controlled or malicious app already running on the host (assessed as local, PR:L, not remote despite the vendor's AV:N/PR:N vector) and depends on winning a narrow timing window, which limits reliability. Impact is confidentiality-only - no integrity or availability effect - and no public exploit has been identified at time of analysis; EPSS is 0.14% (4th percentile), so opportunistic exploitation is unlikely, though the data-disclosure impact and Apple's ecosystem prominence keep patching worthwhile.