Information Disclosure
Monthly
Uncontrolled Recursion in Apache Lucy, a retired full-text search library, enables remote unauthenticated attackers to crash the service via a crafted input, resulting in a complete denial of availability across all versions ever released. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) confirms low-complexity, unauthenticated network exploitation with no confidentiality or integrity impact. No patch exists or will be issued by the Apache Software Foundation, as the project is officially retired; EPSS is low at 0.15% (5th percentile) and no active exploitation (CISA KEV) has been identified at time of analysis.
SQL injection in the Ajax Load More WordPress plugin before 8.0.1 lets unauthenticated attackers inject into an unsanitised parameter used in a database query, enabling time-based blind extraction of sensitive data such as user credentials and secrets. Reported by WPScan with publicly available exploit detail and a vendor patch in 8.0.1; scored CVSS 9.1 with an unauthenticated network vector. EPSS is low (0.19%, 9th percentile), indicating limited observed exploitation despite the critical rating.
Password-protected block content in the Passster WordPress plugin (all versions before 4.3.6) is rendered into the public HTTP response body before the server evaluates the password check, making the gate purely cosmetic. Unauthenticated remote users can retrieve protected content by inspecting the raw response - no password required. A public proof-of-concept exploit is available via WPScan, and the CVSS 3.1 score of 7.5 (AV:N/AC:L/PR:N/UI:N) confirms trivial remote exploitation with full confidentiality impact, though EPSS at 0.16% (5th percentile) and no CISA KEV listing indicate exploitation has not yet become widespread or automated.
Category-locked content in the Passster WordPress plugin (all versions before 4.3.6) is fully exposed through the native WordPress REST API, bypassing the plugin's access controls entirely. Unauthenticated remote users can retrieve the title, full body, and excerpt of any post that site owners intended to restrict using Passster's category-based protection. A publicly available exploit exists per WPScan; no CISA KEV listing and a low EPSS of 0.16% (5th percentile) indicate limited observed in-the-wild exploitation so far, but the trivial exploitation conditions make this an immediate upgrade priority for any site relying on Passster to gate sensitive content.
Unauthenticated content disclosure in the Passster WordPress plugin (versions before 4.3.6) allows any remote user to retrieve the full content of draft, private, and pending posts via a REST API endpoint that skips post-status validation. The flaw is conditional on the target site having a captcha provider configured, which is the typical deployment mode for Passster installations. Publicly available exploit code exists per WPScan reporting, though EPSS sits at only 0.16% (5th percentile), suggesting exploitation remains targeted rather than widespread. No CISA KEV listing has been issued.
Account takeover in the Membership Plugin - Kadence Memberships (formerly Restrict Content) for WordPress affects all versions through 4.0.0 via password-reset link poisoning. The legacy lost-password handler trusts an attacker-controlled rc_redirect POST value, so an unauthenticated attacker can trigger a reset email for any account (including administrators) whose reset link points at an attacker-controlled host carrying a valid key/login; when the victim clicks it, the reset key leaks and can be replayed to seize the account. No public exploit identified at time of analysis, and the flaw is not in CISA KEV, but Wordfence-confirmed root cause and a straightforward primitive make this a high-priority patch (CVSS 9.3).
Remote code execution as root is achievable against H3C NX15 firmware V100R017 via the `/api/esps` Web API endpoint, which exposes the `service.add` function without adequate access controls (CWE-749). Exploitation requires high-privilege authentication, but a post-authentication proof-of-concept script (`postauth_service_add_rce.py`) is publicly available on GitHub, demonstrating a complete root RCE chain. No vendor patch has been identified at time of analysis; no active exploitation is confirmed in CISA KEV.
Out-of-bounds read in S2OPC Toolkit 1.7.3's RepublishResponse message handler enables unauthenticated remote attackers to crash the OPC UA service via a crafted network message, resulting in denial of service. The vulnerable code paths span the subscription publish service layer (msg_subscription_publish_bs.c, msg_subscription_publish_ack_bs.c) and the common encoder module (sopc_encoder.c). No public exploit code or CISA KEV listing exists at time of analysis, but the CVSS:3.1 AV:N/AC:L/PR:N/UI:N vector indicates low-barrier remote exploitation requiring no authentication against reachable OPC UA endpoints.
Incorrect buffer size calculation (CWE-131) in an unidentified Linux distribution package tracked by both Ubuntu and Red Hat enables local, user-interaction-triggered exploitation with high confidentiality, integrity, and availability impact, yielding a CVSS base score of 7.8. The local attack vector combined with a user-interaction requirement (AV:L/UI:R/PR:N) is consistent with a malicious file parsing scenario, where a user opens a crafted input triggering the buffer miscalculation. No public exploit has been identified at time of analysis, and no KEV listing is present; however, the full C:H/I:H/A:H impact triad indicates potential for memory corruption leading to arbitrary code execution.
Improper TLS certificate validation in multiple Lenovo XClarity Orchestrator (LXCO) 2.2.0 microservices exposes sensitive management communications to interception by an adjacent network attacker capable of positioning themselves for a machine-in-the-middle attack. The flaw (CWE-295) allows the attacker to bypass HTTPS trust enforcement under unspecified triggering circumstances, potentially capturing credentials, tokens, or orchestration data exchanged between LXCO microservices. No public exploit code or CISA KEV listing exists at time of analysis; Lenovo has released a patch via advisory HT509976.
Unauthenticated OAuth2 access-token theft in Flowise (npm/flowise <= 3.1.2) stems from the token-refresh endpoint POST /api/v1/oauth2-credential/refresh/:credentialId being listed in WHITELIST_URLS, so it bypasses authentication entirely. Any remote party who knows or guesses a credential ID can force the server to decrypt the stored OAuth2 credential, refresh it against the provider using the victim's client secret, and receive the fresh access_token directly in the response body. No public exploit code has been identified, but the researcher (Shinobi Security) validated the missing-auth behavior in Docker, and a vendor-released patch is available in 3.1.3.
Out-of-bounds read in SSSD's PAM responder allows a local low-privileged attacker to crash the SSSD process and disclose sensitive memory contents by sending a crafted protocol v1 authentication request. Affected systems span all major Red Hat Enterprise Linux releases (6 through 10) and OpenShift Container Platform 4, representing a broad footprint in enterprise Linux environments. No active exploitation is confirmed (not listed in CISA KEV), and the EPSS score of 0.14% at the 3rd percentile reflects a very low observed exploitation probability at time of analysis.
Broken access control in Flowise's GET /api/v1/upsert-history API endpoint exposes the entire server-wide upsert history - exceeding 100MB per response - to any authenticated user, leaking sensitive infrastructure credentials including Qdrant server URLs, collection names, and vector pipeline configuration across all tenants and workspaces. The vulnerability is confirmed in flowise <= 3.1.2 and publicly documented in GHSA-fr6g-7cq8-fg82 with a working curl-based proof-of-concept, meaning any account holder on a multi-tenant deployment can harvest cross-tenant vector store configuration for reconnaissance or targeted follow-on attacks against exposed backends. Vendor-released patch flowise@3.1.3 is confirmed available and addresses missing workspace-scoping enforcement across multiple API controllers.
Remote code execution, data tampering, denial of service, and information disclosure are possible through vulnerabilities in NVIDIA Dynamo for Linux examples and recipes, affecting all versions through v1.1.0. The root cause is CWE-1357 (Relies on Insufficiently Trustworthy Component), meaning the examples or recipes bundle or reference a dependency or component without adequate integrity or trust verification, enabling an attacker to exploit that trust boundary over a network. No public exploit code exists and no active exploitation has been confirmed; EPSS places probability at 0.36% (29th percentile) and SSVC confirms exploitation status as none with a non-automatable attack path, suggesting low near-term weaponization risk despite the high CVSS base score.
Server-side request forgery in NVIDIA Dynamo's Rust multimodal media fetcher (Linux, versions through v1.1.0) allows unauthenticated remote attackers to coerce the server into issuing arbitrary HTTP requests to attacker-controlled destinations. A successful exploit can expose sensitive internal network resources, cloud metadata endpoints (e.g., IMDS at 169.254.169.254), or internal API responses, resulting in high-confidence information disclosure. No public exploit code or CISA KEV listing exists at time of analysis.
Server-side request forgery via DNS rebinding in NVIDIA Dynamo's multimodal media fetcher exposes internal network resources to remote unauthenticated attackers. All Dynamo releases from version 0 through v1.1.0 on Linux are affected. A successful exploit allows an attacker to manipulate the media fetcher into issuing HTTP requests to internal services, leading to high-confidence information disclosure - including potentially cloud metadata endpoints, internal APIs, or adjacent microservices. No public exploit code and no CISA KEV listing have been identified at time of analysis, though the CVSS 7.5 rating and unauthenticated network vector make this a meaningful risk in exposed deployments.
Server-side request forgery in NVIDIA Dynamo's multimodal media fetcher (Linux, versions through v1.1.0) allows unauthenticated remote attackers to issue arbitrary server-side HTTP requests by supplying malicious URLs as media inputs during inference. The CVSS 3.1 vector confirms network-accessible, zero-authentication exploitation with high confidentiality impact, scoring 7.5. No active exploitation or public exploit code has been identified at time of analysis, but SSRF in cloud-hosted AI inference infrastructure carries meaningful risk due to cloud metadata service exposure.
Server-side request forgery in NVIDIA Dynamo for Linux (all versions through v1.1.0) allows unauthenticated remote attackers to force the inference server to issue arbitrary HTTP requests by embedding a crafted URL inside a multimodal inference request payload. Successful exploitation exposes internal network resources reachable from the Dynamo host, producing high-severity information disclosure without requiring any credentials or user interaction. No public exploit code or CISA KEV listing has been identified at time of analysis, though the PR:N/AC:L attack surface on AI serving endpoints that may be network-exposed warrants prompt remediation.
Server-side request forgery in NVIDIA Dynamo for Linux (versions 0 through v1.1.0) enables unauthenticated remote attackers to cause the server to issue arbitrary backend HTTP requests. The CVSS:3.1 vector (AV:N/AC:L/PR:N/UI:N) confirms network-exploitable with no authentication or user interaction required, making this accessible to any attacker who can reach the Dynamo service. Successful exploitation leads to confidentiality impact - likely exposure of internal services, cloud instance metadata endpoints, or internal API responses - with no public exploit or CISA KEV listing identified at time of analysis.
Server-side request forgery in NVIDIA Dynamo for Linux (versions through v1.1.0) allows unauthenticated remote attackers to read arbitrary local files by embedding a crafted local path inside a multimodal inference request. The Dynamo serving layer fails to restrict the path to an allowed directory, causing the server to resolve and return content from restricted filesystem locations, leading to high-confidentiality information disclosure. No public exploit code or CISA KEV listing has been identified at time of analysis; however, the low attack complexity and lack of authentication requirements make this straightforward to exploit against any exposed Dynamo endpoint.
Path traversal in NVIDIA Dynamo's image loading component on Linux enables unauthenticated remote attackers to read arbitrary files outside the intended restricted directory, resulting in high-severity information disclosure. All releases from version 0 through v1.0.0 are affected, per EUVD-2026-52804 and the NVIDIA product security advisory. No public exploit code or active exploitation has been identified at time of analysis, though the CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates low-complexity, authentication-free exploitation against any network-exposed instance.
Hash collision exploitation in NVIDIA Dynamo's multimodal embedding cache on Linux allows unauthenticated remote attackers to corrupt cached inference data by submitting specially crafted images. The cache fails to incorporate image dimensions into its hash function, meaning two images with identical pixel byte sequences but different spatial dimensions resolve to the same cache key, causing the wrong embedding to be served for subsequent requests. No public exploit code has been identified and this vulnerability is not listed in the CISA KEV catalog, but the CVSS score of 7.5 with no authentication requirement (PR:N) elevates its priority in deployments where the inference API is network-accessible.
Out-of-bounds write in the multimodal serving topology of NVIDIA Dynamo for Linux allows remote unauthenticated attackers to corrupt memory, with a rated 9.8 CVSS potentially enabling remote code execution, privilege escalation, data tampering, information disclosure, and denial of service. NVIDIA (the reporting vendor) rates it critical with a network-reachable, no-privilege, no-interaction vector. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, so the score reflects potential rather than observed impact.
Path traversal in NVIDIA Triton Inference Server's MLflow plugin allows a low-privileged local user to read, write, or modify files outside the designated model repository by embedding traversal sequences in a model name parameter. All Linux deployments of Triton Inference Server through version 26.02 are affected. No active exploitation has been confirmed (not listed in CISA KEV), EPSS is 0.16% (6th percentile), and SSVC rates exploitation status as none - indicating this is a real but currently low-observed-risk vulnerability that warrants patching on a standard cadence rather than emergency response.
Flowise's patch for CVE-2025-8943 is fully bypassed in versions up to and including 3.1.2, allowing unauthenticated remote code execution on default deployments via the npm_config_yes environment variable. The prior mitigation blocked the -y and --yes flags on npx and denied four specific environment variable names by exact string match, but npm natively reads its configuration from any npm_config_* prefixed variable, making npm_config_yes=true semantically equivalent to --yes. Any attacker who can submit a Custom MCP stdio server configuration - which requires no authentication on default Flowise deployments - can force npx to auto-install and execute an arbitrary package as the Flowise server process. No public exploit code has been identified at time of analysis, though the bypass technique is fully documented in the public GHSA advisory GHSA-xc48-889x-5qmw, making independent weaponization trivial.
Credential theft via agent impersonation in Veeam Service Provider Console (VSPC) allows a remote, unauthenticated attacker to masquerade as a legitimately managed backup agent and harvest that agent's credentials. Because VSPC is the multi-tenant management plane MSPs use to orchestrate backups across customer estates, captured agent credentials give an attacker a foothold to pivot into managed endpoints. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but the vendor rates it critical (9.5) and CWE-288 identifies an authentication-bypass root cause.
Memory exhaustion in Veeam Service Provider Console (VSPC) allows unauthenticated remote attackers to deplete host memory and cause a denial of service, with no authentication or user interaction required. The CVSS 4.0 score of 8.7 reflects the network-accessible, zero-prerequisite nature of exploitation (AV:N/AC:L/AT:N/PR:N/UI:N) with high availability impact confined to the vulnerable system. No public exploit code and no CISA KEV listing have been identified at time of analysis, but the low exploitation barrier makes any internet-exposed VSPC instance a realistic target.
Qualcomm Snapdragon chipsets fail to verify the consistency of UE security capabilities against those replayed by the network during 3GPP cellular security mode negotiation, enabling a rogue base station operator to force downgraded cryptographic algorithm selection on unpatched devices. The flaw resides in the cellular modem firmware stack and affects all Snapdragon product lines per available CPE data, with no minimum version boundary published. Exploitation yields high confidentiality impact - a sophisticated attacker with radio interception equipment can potentially decrypt cellular communications. No public exploit code and no CISA KEV listing have been identified at time of analysis, though the underlying attack class (security capability bidding-down) is well-documented in cellular security research.
pardus-image-writer before 1.0.4, developed by TÜBİTAK BİLGEM Software Technologies Research Institute for Turkey's national Pardus Linux distribution, permits external control of file name or path (CWE-73), enabling a locally authenticated attacker to redirect file operations outside their intended scope and remove important client functionality. The CVSS vector (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H, score 7.1) confirms that standard user privileges and no interaction from other users are required, with high integrity and availability impact but no confidentiality impact. No public exploit code or active exploitation has been identified at time of analysis; this is a Turkish CERT (USOM)-reported vulnerability with a confirmed fix at version 1.0.4.
Unauthenticated remote denial-of-service in Eclipse Milo 0.6.0-1.1.4 allows any network-accessible client to exhaust the OPC UA server's off-heap direct memory pool by repeatedly sending incomplete UASC message chunks and disconnecting before message assembly completes. The UASC server-side asymmetric handler and ChunkDecoder fail to invoke ReferenceCountUtil.safeRelease() on retained Netty ByteBuf objects when the channel lifecycle ends, causing unbounded off-heap memory accumulation. No authentication is required and no special server configuration is necessary; the fix commit is publicly available on GitHub, serving as an effective blueprint for exploitation, though no standalone POC tool or CISA KEV listing has been identified at time of analysis.
Password recovery in Eclipse Milo (the open-source OPC UA SDK for Java) versions 0.6.0 through 1.1.4 allows an on-path attacker to break username-token confidentiality via a Bleichenbacher-style padding oracle. The server returns distinguishable error responses for invalid RSA PKCS#1 v1.5 padding versus other authentication failures during username-token processing, so an attacker who captures a victim's Basic128Rsa15-encrypted username token can send repeated unauthenticated ActivateSession requests to recover the cleartext password and then authenticate as the victim. No public exploit identified at time of analysis and it is not listed in CISA KEV; the weakness and its upstream fix are confirmed by the Eclipse Foundation.
Session hijacking is possible in HUMANIST Digital Human Resources (versions 26.0 through before 26.1) due to sensitive session tokens being transmitted as GET request query string parameters. Exposure occurs through server access logs, browser history, and HTTP Referer headers leaking to downstream systems. No public exploit code has been identified at time of analysis, and no CISA KEV listing exists, but the CVSS integrity and confidentiality impact ratings are both High, reflecting full session takeover potential.
Sensitive-data exposure in Bilin Software's HUMANIST Digital Human Resources (versions 26.0 up to but not including 26.1) stems from a cryptographic key embedded directly in the application binary, letting attackers recover the same static key from any deployment and abuse it against protected data. Because the key is identical across all installations, its extraction undermines confidentiality and integrity of anything it protects. No public exploit identified at time of analysis, and the flaw was reported through Turkey's national CSIRT (TR-CERT).
Hard-coded RSA private key exposure in GeoVision GV-AS1620 (GV-Cloud) access-control appliances lets remote attackers decrypt and forge the device's HTTPS traffic. The firmware ships an embedded, static RSA private key used by the built-in Lighttpd web server for TLS termination, so anyone who extracts it from one device can passively decrypt or actively impersonate the management interface of every device sharing that key. No public exploit identified at time of analysis, but the shared-secret nature makes the flaw broadly reusable once the key is recovered.
Hard-coded RSA private key exposure in the GeoVision GV-AS1620 (AS Manager) access-control device lets attackers who extract the firmware-embedded key decrypt and forge the Lighttpd TLS session used for the device's HTTPS management interface. Because the key is static and shared across all units of the same firmware, a single extraction compromises every deployed device, enabling passive traffic decryption and active server impersonation. No public exploit is identified at time of analysis, and the issue is not listed in CISA KEV.
Kernel memory corruption in the Linux kernel SCTP stack allows a remote peer to trigger a use-after-free during ASCONF DEL-IP processing, corrupting an association's transport list and leaving primary_path/active_path pointing at freed memory. The flaw affects the SCTP dynamic address reconfiguration (ASCONF) path across a wide range of kernel versions and, given kernel-level impact, can lead to denial of service and potentially privilege escalation or code execution. Despite the 9.8 CVSS and 'Information Disclosure' tag, there is no public exploit identified at time of analysis and EPSS is low (0.16%), reflecting the SCTP/ASCONF-specific conditions required.
Race condition in the Linux kernel's KVM nVMX (nested VMX) subsystem allows a low-privileged local attacker to trigger a use-after-free via shadow VMCS teardown, with potential for full hypervisor compromise. The flaw arises because free_nested() releases the shadow VMCS page while vmcs01 still holds a dangling pointer; if the vCPU migrates to another physical CPU before the pointer is cleared, __loaded_vmcs_clear() executes VMCLEAR against the freed page, corrupting kernel memory. No public exploit code exists and no active exploitation is confirmed (EPSS 0.16%, 5th percentile), but the S:C scope change in the CVSS vector and the C:H/I:H/A:H impact triad indicate this could enable a guest-to-host escape under the right conditions.
Shadow MMU ordering flaw in the Linux kernel KVM x86 subsystem allows a low-privileged guest process to corrupt the hypervisor's page table state by triggering invalid root population during shadow page reclamation. Kernels from 5.9 through multiple unpatched stable branches permit child shadow pages to be created under an invalidated parent root, violating a core MMU invariant and potentially enabling guest-to-host privilege escalation. No public exploit has been identified and EPSS is low (0.16%), but the confirmed scope change to the host hypervisor makes this a high-priority patch for any KVM-based multi-tenant or cloud virtualization environment.
Out-of-bounds read in open62541 1.5.5 allows a malicious OPC UA server to crash connecting clients via a crafted namespace array response. The flaw resides in the client-side connection handler responseReadNamespacesArray() in src/client/ua_client_connect.c, triggered during the namespace discovery phase of the OPC UA session establishment. With a CVSS availability impact of High and no privileges required on the attacker side, the practical effect is a remotely-induced denial of service against any open62541-based OPC UA client that connects to an attacker-controlled server. No public exploit identified at time of analysis.
Microsoft Edge for Android exposes device file contents to remote attackers through an external file path control flaw (CWE-73), enabling information disclosure across a scope boundary. The CVSS vector (S:C, C:H) confirms the vulnerability crosses from the browser sandbox into the broader Android file system or other protected resources. No public exploit code exists and an official vendor fix is available; exploitation requires user interaction, making this a meaningful but not critical-priority risk for most deployments.
External file path control in Microsoft Edge for Android (versions below 151.0.4129.59) allows a local low-privileged attacker to disclose sensitive information stored on the device. Rooted in CWE-73, the flaw permits attacker-controlled input to dictate file name or path resolution within the browser, potentially exposing files outside the intended access scope. No public exploit identified at time of analysis, and SSVC confirms no known exploitation; however, the CVSS C:H and I:H ratings suggest the path control primitive may extend beyond read-only disclosure.
Origin validation bypass in Microsoft Edge (Chromium-based) enables a remote, unauthenticated attacker to circumvent Same-Origin Policy protections, resulting in unauthorized cross-origin access to sensitive data. The flaw (CWE-346) affects all versions of Chromium-based Edge and carries a vendor CVSS of 8.1 with both high confidentiality and high integrity impact - the latter is notable given the description characterizes this as an information disclosure issue, a discrepancy that warrants verification against the MSRC advisory. No public exploit code exists and the vulnerability is not listed in CISA KEV; Microsoft has released an official patch.
JSON-LD signature validation in Misskey's ActivityPub federation layer accepts fraudulent federated activities due to a TOCTOU flaw where the JSON-LD parsing context used during signature verification is not shared with the context used during subsequent message processing. Affected are all self-hosted Misskey instances running versions 12.37.0 through 2026.5.3. A remote, unauthenticated attacker operating or spoofing a federated server can craft payloads that pass signature checks yet resolve to malicious content during processing, resulting in high integrity impact across the instance and potentially propagating to federated peers; no public exploit or CISA KEV listing has been identified at time of analysis.
Signature validation bypass in Misskey (versions 12.37.0 through prior to 2026.5.4) allows an attacker to have spoofed ActivityPub activities accepted as authentic. The flaw resides in the JSON-LD signature validation and compaction logic (CWE-347), enabling forgery of federated actions such as posts or actions attributed to other actors/instances. The CVSS 4.0 base score is 9.2 (Critical) with a network, unauthenticated, low-complexity vector emphasizing integrity impact; no public exploit has been identified at time of analysis, and it is not listed in CISA KEV.
PKCS#7 EnvelopedData decryption in the Python cryptography library (versions 44.0.0-49.x) leaks a Bleichenbacher oracle through four distinguishable error messages and timing side-channels during RSA PKCS#1 v1.5 key unwrapping, exposing the exact recovered plaintext length in one case. An attacker who can submit crafted EnvelopedData to an auto-decrypting service - such as an S/MIME gateway or mail filter that reflects outcomes at high volume - can adaptively recover the content-encryption key and decrypt intercepted messages. No public exploit has been identified at time of analysis, and exploitation requires very specific deployment conditions; the fix in version 50.0.0 applies RFC 3218 indistinguishability by substituting a random key on any failure.
Host confusion in GuzzleHttp Guzzle before 7.15.2 and 8.0.1 allows remote attackers who can influence a fetched URI to bypass application-level host validation and reach network hosts the application intended to block, including loopback and internal addresses. The divergence occurs because PHP's filter_var() and Guzzle's own host checks operate on the literal URI text while libcurl independently percent-decodes and IDNA-maps the authority before resolving and connecting, meaning the application and transport disagree on which host is being contacted. No public exploit has been identified and the vulnerability is absent from the CISA KEV catalog, but any application that implements SSRF mitigations via URI host inspection before passing a user-supplied URL to Guzzle is directly undermined.
Blind SQL injection in Shlink's tag statistics REST endpoint allows any API key holder to extract sensitive data from the underlying database across all tenants. The unvalidated `direction` value of the `orderBy` query parameter flows unsanitized into a Doctrine QueryBuilder ORDER BY clause, enabling time-based, boolean-oracle, and error-based extraction of long URLs, visitor records, IP addresses, geolocation data, user agents, and hashed API key secrets. A public proof-of-concept exploit is available on GitHub, no public exploit identified at time of analysis as confirmed actively exploited, but the low barrier to exploitation - any valid API key suffices - makes this a genuine remediation priority for Shlink operators.
Uncontrolled decompression in Apache NiFi 1.5.0 through 2.10.0 exposes the REST API to unauthenticated denial-of-service attacks via crafted gzip payloads. The Jersey encoding filter enforces its configurable size limit against the compressed form of the request body rather than the decompressed output, enabling a classic zip-bomb condition that can exhaust JVM heap memory. No public exploit has been identified at time of analysis, but the CVSS 4.0 supplemental metadata flags the attack as automatable (AU:Y) with Amber utility, indicating meaningful real-world risk against organizations with network-accessible NiFi REST API endpoints.
Memory exhaustion via malformed binary attachment packets in the socket.io-parser npm library allows unauthenticated remote attackers to crash or hang Socket.IO servers. By sending crafted packets that declare a large number of pending binary attachments, an attacker causes the server's Decoder to allocate and hold buffers indefinitely, exhausting Node.js heap memory. The vendor advisory (GHSA-2m8v-j782-fhvr) confirms the impact and vendor-released fixed versions are available; no public exploit code or CISA KEV listing has been identified at time of analysis.
Injection vulnerability in GL-iNet GL-MT3000 (Beryl AX) firmware through version 4.4.5 exposes the plugins.set_config function via /cgi-bin/glc to remote exploitation with no authentication or user interaction required per the CVSS 4.0 vector. Successful exploitation yields high confidentiality, integrity, and availability impact on the device, consistent with OS command or argument injection against the native plugin handler. A proof-of-concept exploit is publicly available on GitHub and the vendor has confirmed the vulnerability, though no patch has been released at time of analysis.
Local privilege escalation in Dell Monitor Driver exploits a symlink (link-following) flaw to allow a low-privileged local attacker to elevate to higher system privileges, achieving full confidentiality, integrity, and availability impact on the host. The vendor has released a patch via Dell Security Advisory DSA-2026-295, and no public exploit code has been identified at time of analysis. EPSS rates exploitation probability at 0.11% (2nd percentile), and SSVC classifies exploitation as none and automatable as no - consistent with the local-only attack vector and the absence of CISA KEV listing.
HttpTransferCache key collision in Angular's Server-Side Rendering subsystem enables cache poisoning by exploiting identical serialization of scalar comma-separated query parameters and semantically distinct repeated query parameters against the same endpoint. Angular SSR applications using client-side hydration across versions 20.x, 21.x, and 22.x - and 19.x with no available patch - are at risk of having security-sensitive HttpClient responses silently replaced by earlier attacker-influenced cached responses, bypassing trusted backend authorization calls entirely. Vendor patches 22.0.2, 21.2.19, and 20.3.27 are confirmed available; no public exploit code and no CISA KEV listing exist at time of analysis.
Information disclosure in SiYuan (a personal knowledge-management/note-taking application) before v3.7.3 lets anonymous readers or low-privilege publish RoleReader tokens read the full rendered content of documents that were explicitly marked publish-disabled. The getHeadingDeleteTransaction, getHeadingLevelTransaction, and getHeadingInsertTransaction endpoints return rendered block DOM without enforcing publish-access checks, so supplying a target heading block ID leaks restricted content. Reported by VulnCheck with a vendor patch available; no public exploit identified at time of analysis, and this is not listed in CISA KEV.
Uncontrolled recursion in Bouncy Castle for Java's lazy ASN.1 parser enables remote unauthenticated denial of service across all three library release lines (bc-java, bc-lts-java, and bc-fja FIPS). When a LazyEncodedSequence is forced during tree traversal, it resets the nesting-depth guard to its configured maximum instead of continuing with the remaining depth budget, allowing crafted deeply-nested ASN.1 structures to bypass StreamUtil's recursion limit and trigger a StackOverflowError. No public exploit has been identified at time of analysis, but any Java application accepting externally-supplied ASN.1 data - TLS certificates, CMS signatures, PKCS structures - is potentially exposed without authentication.
RSA PKCS#1 v1.5 signature forgery is possible in Bouncy Castle for Java (bc-java before 1.85, bc-lts-java before 2.73.12) when the DigestInfo encoding omits the NULL AlgorithmIdentifier parameter. The off-by-two bytes in the RSADigestSigner comparison loop allows any forged signature whose DigestInfo matches all bytes except the final two of the message hash to pass verification as valid, achieving a high-integrity bypass. No public exploit has been identified at time of analysis, but the public patch commit includes a step-by-step test demonstrating the exact forgery technique, substantially lowering the bar to exploitation.
Heap exhaustion via uncontrolled memory allocation in Bouncy Castle for Java's MLS wire decoder allows remote unauthenticated attackers to crash any application using the bc-java MLS module. The MLSInputStream.readOpaque() method decodes an attacker-supplied Varint length field (up to 0x3FFFFFFF, approximately 1 GiB) and allocates that buffer before verifying the input stream actually contains that many bytes; a handful of concurrent few-byte crafted messages can exhaust the JVM heap. No public exploit has been identified at time of analysis and CISA KEV listing is absent, though the attack is trivially constructable from the published patch and regression test.
OpenPGP AEAD decryption in Bouncy Castle for Java silently bypasses the final authentication tag when plaintext is an exact multiple of the AEAD chunk length, allowing an attacker who can tamper with ciphertext to strip trailing plaintext chunks and have the truncated message accepted as cryptographically authentic. Affected libraries span bc-java before 1.85, bc-lts-java before 2.73.12, and all three active BC-FJA FIPS series before their respective bcpg-fips 1.0.13, 2.0.13, and 2.1.13 releases. No public exploit has been identified at time of analysis and this CVE is not listed in CISA KEV, but the CVSS 4.0 score of 8.7 (Integrity: High) reflects a complete and silent bypass of AEAD integrity guarantees for chunk-aligned messages with no downstream exception or warning.
IESEngine in Bouncy Castle for Java allows cross-message MAC forgery when stream mode is used with static key pairs, affecting bc-java before 1.85 and bc-lts-java before 2.73.12. The flaw stems from a length-dependent KDF output split: in the static-key path (no ephemeral V component), the MAC key K2 was placed at a byte offset equal to the message length after the keystream K1, so an observer of one known-plaintext encryption can recover K2 and forge valid ciphertext-plus-tag pairs for shorter messages. No public exploit beyond the vendor's own proof-of-concept regression test exists, and no CISA KEV listing is present at time of analysis.
Cross-nonce AEAD forgery in Bouncy Castle for Java's KCCMBlockCipher (DSTU 7624 CCM mode) allows an attacker with chosen-plaintext oracle access to forge valid authenticated ciphertext under an un-queried nonce when no associated authenticated data is present. All bc-java releases before 1.85 and bc-lts-java releases before 2.73.12 are affected. The G1 initialization block - which binds the nonce into the MAC under the DSTU 7624:2014 standard - was conditionally skipped when no AAD bytes were supplied, leaving the authentication tag independent of the nonce and breaking the core AEAD security guarantee. No public exploit has been independently released and this vulnerability is not listed in CISA KEV, though the fix commits include a working regression test that fully demonstrates the forgery technique.
CMS AuthEnvelopedData decryption in Bouncy Castle for Java fails to enforce a minimum AEAD authentication tag length, allowing a network attacker to supply a crafted CMS message carrying a truncated AES-GCM/CCM ICV (e.g., 32 bits instead of the standard 128 bits), effectively reducing the authentication space to the point where tag forgery becomes computationally feasible. Affected are bc-java before 1.85, bc-lts-java before 2.73.12, and all bc-fja (FIPS) 1.0.x/2.0.x/2.1.x series before their respective .12 patch releases. No public exploit or CISA KEV listing has been identified at time of analysis, but the CVSS 4.0 score of 8.7 with VI:H reflects the high integrity impact of bypassing authenticated encryption guarantees.
Out-of-memory denial-of-service in Bouncy Castle for Java allows remote unauthenticated attackers to crash Java applications by submitting a crafted ASN.1 definite-length object with an inflated declared size. The ASN.1 parser in `DefiniteLengthInputStream.toByteArray()` allocated a full heap-sized byte array before reading any body bytes, meaning a few-byte header claiming a near-JVM-heap payload was sufficient to trigger OOM. All major Bouncy Castle release lines are affected - including the FIPS-certified BC-FJA variant - and a vendor patch is available; no public exploit code or CISA KEV listing exists at time of analysis.
CPU exhaustion in Bouncy Castle for Java allows remote attackers to cause denial of service by supplying X.500 distinguished name attribute values densely packed with RFC 4514 special characters or leading/trailing spaces. The root cause is a quadratic-time O(n²) escaping algorithm in `IETFUtils.valueToString()` that inserts backslashes into the buffer being actively scanned - triggerable through `X500Name.toString()`, `.equals()`, or `.hashCode()`, methods commonly invoked during TLS certificate and LDAP DN processing. No public exploit has been identified beyond the vendor's own regression test, and this vulnerability is not listed in CISA KEV, though the CVSS 4.0 score of 8.7 with AV:N/PR:N signals meaningful exposure for Internet-facing Java services.
Uncontrolled memory allocation in Bouncy Castle for Java's HSS public-key parser allows remote unauthenticated attackers to exhaust JVM heap memory by supplying a crafted public key with an arbitrarily large HSS level count (L value), causing denial of service during signature verification. All three product lines are affected: bc-java before 1.85, bc-lts-java before 2.73.12, and BC-FIPS (bc-fja) before 2.0.2/2.1.3 depending on series. No public exploit has been identified at time of analysis and no CISA KEV listing exists, but the AV:N/AC:L/PR:N attack profile and Bouncy Castle's ubiquity as a Java crypto dependency make this a credible availability risk for any service accepting external HSS/LMS key material.
CCMBlockCipher in Bouncy Castle for Java decrypts ciphertext directly into the caller-supplied output buffer before verifying the authentication tag, leaving unverified CTR-decrypted plaintext in memory when tag verification fails and violating NIST SP 800-38C §6.2. Every edition - bc-java before 1.85, bc-lts-java before 2.73.12, and BC-FJA across three active release lines (1.0.x, 2.0.x, 2.1.x) - is affected. Applications that reuse pooled byte buffers, log failure-path output, or otherwise expose the buffer on an authentication failure inadvertently become CTR decryption oracles, allowing attackers to submit forged ciphertexts and recover plaintext without possessing a valid authentication tag. No public exploit and no CISA KEV listing exist at time of analysis.
Certificate revocation-check bypass in the Bouncy Castle for Java (bc-java) PKIX provider allows a validly-signed OCSP response issued for one certificate to be accepted as proof-of-status for a different certificate, because the stapled response is not bound to the CertID of the certificate actually being checked. This means a revoked end-entity certificate can pass PKIXRevocationChecker validation when a 'good' OCSP response for another serial (e.g. the CA's) is supplied, defeating revocation enforcement in TLS/PKI clients that rely on OCSP stapling. Affected releases are bc-java before 1.85, bc-lts-java before 2.73.12, and BC-FJA (FIPS) before 2.0.2 and 2.1.3; no public exploit identified at time of analysis and it is not listed in CISA KEV.
Out-of-bounds read in MediaTek modem firmware across 19 chipsets enables remote denial of service when a User Equipment (UE) is connected to an attacker-controlled rogue base station. The flaw stems from a missing bounds check (CWE-125) in modem protocol processing, crashing or disrupting the modem without requiring any user interaction or device-side privileges. No active exploitation is confirmed (no CISA KEV listing), and EPSS probability is very low at 0.21% (11th percentile), consistent with SSVC's 'exploitation: none' status - though the attack is classified as automatable once rogue infrastructure is in place.
TLS hostname-verification bypass in the Bouncy Castle for Java JSSE provider (BCJSSE) ships the legacy certificate-CN fallback enabled by default, even though the vendor documentation states it is opt-in and gated behind the org.bouncycastle.jsse.client.checkCnFallback property. Affected are BC-Java before 1.85, BC-LTS before 2.73.12, and BC-FJA (FIPS) TLS module bctls-fips before 1.0.24, 2.0.24 and 2.1.24; a MITM-positioned attacker can present a SAN-less certificate whose Subject CN names the victim host and have it silently accepted, defeating name-constraint protections and enabling interception of TLS traffic (CWE-297). This carries a CVSS 4.0 base of 9.3, but there is no public exploit identified at time of analysis and it is not in CISA KEV.
Signature bypass in Bouncy Castle for Java allows any attacker-supplied content wrapped in a zero-signer CMS envelope to pass `CMSSignedData.verifySignatures()` without any valid cryptographic signature. The method iterates an empty signerInfos SET, falls through to a vacuous `return true`, and any application using it as its top-level authenticity check silently accepts unsigned attacker-controlled content as authenticated - a classic fail-open flaw (CWE-347). No public exploit has been identified at time of analysis and the vulnerability is not listed in CISA KEV, but the attack primitive is trivially constructible using any standard CMS/PKCS#7 library.
Bouncy Castle for Java's OpenPGP session-key decryption path re-exposes the Mister-Zuccherato adaptive-chosen-ciphertext oracle by failing to suppress the legacy CFB 'quick check' on the PKESK/session-key route, enabling an attacker with decryption oracle access to recover plaintext from SEIPD v1 encrypted messages. Affected are bc-java before 1.85, bc-lts-java before 2.73.12, and BC-FJA (bcpg-fips) across the 1.0.X, 2.0.X, and 2.1.X series - three distinct product lines used broadly in enterprise and open-source Java applications. No public exploit or CISA KEV listing has been identified at time of analysis; however, the attack technique is well-established in cryptographic literature dating to the Mister-Zuccherato paper.
Signature forgery via back-dated signingTime in Bouncy Castle's S/MIME validator allows an attacker holding a revoked or expired signing certificate to have that certificate accepted as valid by unpatched validators. The SignedMailValidator in bc-java before 1.85, bc-lts-java before 2.73.12, and all bc-fja (FIPS) lines before their respective 1.0.7/2.0.7/2.1.7 fixes unconditionally used the signer-asserted CMS signingTime attribute as the PKIX path-validation date, making certificate expiry and revocation checks bypassable. No public exploit or CISA KEV listing exists at time of analysis, but the flaw is architecturally straightforward to exploit by any party that holds or has previously held a Bouncy Castle-validated signing certificate.
CMS AuthenticatedData integrity verification in Bouncy Castle for Java is bypassable when authenticated attributes (authAttrs) are present, allowing an attacker to substitute arbitrary content while the recipient MAC check passes without error. Affected are bc-java before 1.85, bc-lts-java before 2.73.12, and BC-FJA across the 1.0.x, 2.0.x, and 2.1.x series - all widely deployed in Java enterprise and FIPS environments. The CVSS 4.0 vector (AV:N/AC:L/PR:N/UI:N/VI:H) reflects unauthenticated remote exploitation with high integrity impact; no public exploit or CISA KEV listing is confirmed at time of analysis.
OpenPGP inline-signature policy enforcement in Bouncy Castle for Java silently discards rejection exceptions, causing signatures that use prohibited weak hash algorithms (MD5, SHA-1, RIPEMD-160) or otherwise violate the configured OpenPGPPolicy to be reported as cryptographically valid. Affected are bc-java before 1.85 and bcpg-fips (bc-fja) before 2.0.13; the detached-signature and prefixed-signature verification paths are not affected - only the inline one-pass path. A vendor patch is available; no public exploit code has been identified at time of analysis, though the CVSS 4.0 score of 8.7 reflects a high integrity impact driven by the unauthenticated network vector.
CPU exhaustion in Bouncy Castle for Java's MLS (Messaging Layer Security) implementation allows a network attacker to trigger unbounded HKDF key-derivation iterations by supplying a crafted 32-bit generation counter in an MLS message. The hash-ratchet in GroupKeySet.get(int generation) advances one HKDF step per skipped generation without any upper bound, so a maximally crafted counter forces up to ~4.29 billion derivation steps on the receiving process. Scored CVSS 4.0 at 8.7 with High availability impact and no authentication prerequisites per vendor scoring; no public exploit code or KEV listing has been identified at time of analysis.
Unbounded recursion in Bouncy Castle's OER (Octet Encoding Rules) parser enables remote unauthenticated denial-of-service against any Java application processing IEEE 1609.2 V2X messages. Because the IEEE 1609.2 schema is cyclic - an Ieee1609Dot2Data structure can nest inside its own SignedData payload - a few kilobytes of crafted input drive the parser into unbounded recursive descent, terminating in a JVM StackOverflowError. Critically, parsing occurs before signature verification, so no authentication or trust relationship is needed to trigger the crash. No public exploit has been identified at time of analysis, but the patch commit exposes two additional heap-exhaustion vectors alongside the primary recursion flaw, all reachable from the same pre-verification code path.
Memory exhaustion denial-of-service in Bouncy Castle's DTLS implementation allows remote unauthenticated attackers to crash or degrade Java applications by sending crafted handshake messages with inflated 24-bit length fields. Affected are bc-java before 1.85, bc-lts-java before 2.73.12, and BC-FJA (bctls-fips) before 1.0.24, 2.0.24, or 2.1.24 depending on the deployed branch. The buffer allocation occurs pre-authentication during the DTLS handshake reassembly phase - before any signature or Finished verification - making this exploitable without credentials against any exposed DTLS endpoint. No public exploit code has been identified and the vulnerability is not listed in CISA KEV.
Memory exhaustion in Bouncy Castle for Java's OpenPGP parser enables unauthenticated remote denial of service via a crafted User Attribute subpacket with an oversized length header. All Java applications importing untrusted OpenPGP certificates using bc-java before 1.85, bc-lts-java before 2.73.12, or BC-FJA (FIPS) in affected series are vulnerable to pre-authentication JVM heap exhaustion. No KEV listing or public exploit has been confirmed at time of analysis, but the zero-complexity unauthenticated network attack vector and CVSS 4.0 score of 8.7 signal high operational priority for services that accept OpenPGP certificates from external sources.
Private key recovery in Bouncy Castle for Java (bc-java before 1.85, bc-lts-java before 2.73.12) affects the DH agreement code path, where a peer-supplied public value is exponentiated with the local private key without full range/subgroup validation. A malicious protocol peer can submit small-order or out-of-range Diffie-Hellman elements to mount a small-subgroup confinement attack and, when the local private key is static/reused, gradually recover it via CRT - enabling decryption and impersonation. No public exploit identified at time of analysis; the fix is a vendor-released patch and the vulnerability is not listed in CISA KEV.
Bouncy Castle for Java's BKS keystore implementation silently accepted legacy version 0/1 keystores that derive a critically weak 16-bit HMAC integrity key - brute-forceable offline in milliseconds against the 65,536-value keyspace - allowing an attacker who can supply or tamper with a keystore file to forge the integrity MAC, inject rogue trusted certificates, and have the manipulated keystore accepted without error. All bc-java releases before 1.85 and bc-lts-java releases before 2.73.12 are affected. No public exploit code has been identified and this vulnerability does not appear in the CISA KEV catalog at time of analysis.
Bouncy Castle for Java's BKS and UBER keystore implementation crashes with an OutOfMemoryError when loading a crafted keystore because heap allocation from stream-declared lengths occurs before the HMAC integrity check. Any application calling KeyStore.load() with attacker-controlled BKS or UBER keystore data is affected - bc-java before 1.85 and bc-lts-java before 2.73.12. A POC was submitted alongside the report, confirming that a file of just a few dozen bytes declaring Integer.MAX_VALUE-length fields is sufficient to exhaust JVM heap regardless of heap configuration or supplied password. No public exploit identified at time of analysis beyond the researcher's POC referenced in the patch commit.
Forced processor reset in NASA Core Flight System (cFS) v7.0.1 is achievable by supplying a crafted entry to the HS.AppMon_Tbl, exploited through the HS_MonitorApplications() function in the Health and Safety application module. The vulnerability targets embedded real-time flight software used in spacecraft, where an unplanned processor reset can have mission-critical consequences. A proof-of-concept exists per SSVC data, exploitation is rated automatable, and the EPSS score of 0.14% (4th percentile) suggests no widespread opportunistic scanning - consistent with narrow, targeted exploitation in aerospace operational contexts. No active CISA KEV listing has been confirmed.
Unauthenticated remote attackers can manipulate the CCSDS File Delivery Protocol (CFDP) metadata handler in NASA Core Flight System v7.0.1, specifically the CF_CFDP_RecvMd() function, to control the destination path where received file content is stored on the target system, resulting in high-impact information disclosure. A publicly available proof-of-concept exists per SSVC classification, making this exploitable without authentication or user interaction against any network-reachable cFS instance with the CF application enabled. Despite the availability of exploit code and network-accessible attack vector, the EPSS score of 0.14% (4th percentile) reflects the extremely limited real-world deployment footprint of this aerospace-domain platform.
Predictable API key generation in osTicket 1.18.3 lets remote attackers reconstruct valid staff API keys by exploiting weak MD5-based construction seeded with the request timestamp and client IP address (CWE-331). Because the key is derived from low-entropy, guessable inputs, an attacker who approximates the key creation window can brute-force the key space and gain API access without credentials. Rated CVSS 9.8 by the reporter; no public exploit is identified at time of analysis, though a technical disclosure write-up exists, and CISA SSVC lists exploitation as none but marks the flaw automatable with total technical impact.
Stack buffer over-read and stray one-byte NUL write in Zephyr RTOS's experimental OCPP 1.6 client allow a malicious or compromised OCPP central server - or an on-path attacker exploiting the commonly unencrypted ws:// transport - to crash a connected embedded device by sending a crafted WAMP RPC frame with an oversized uid or action field. The vulnerable helper extract_string_field() uses strncpy() without guaranteeing NUL-termination, causing a subsequent strchr() call to scan unbounded into adjacent stack memory; a secondary defect in extract_payload() compounds this on maximal-length frames. No active exploitation has been confirmed by CISA KEV, but SSVC classification indicates publicly available proof-of-concept code, and EPSS sits at a low 0.19% (10th percentile), consistent with a niche embedded RTOS attack surface.
Cleartext leakage of the HA cluster token in ArcadeDB's MCP get_server_settings tool allows any authenticated MCP user to escalate to full root-level server control in all versions before 26.7.3. The exposed arcadedb.ha.clusterToken can be replayed via the X-ArcadeDB-Cluster-Token and X-ArcadeDB-Forwarded-User HTTP headers to impersonate the root user, turning a low-privilege information disclosure into a complete server compromise. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog; however, the chained privilege escalation path significantly elevates real-world impact beyond the CWE-200 classification suggests.
Unauthenticated exposure of OAuth credentials in the Gallery for Google Photos WordPress plugin (all versions before 1.2.1) allows any remote attacker to retrieve the stored Google access and refresh tokens of the connected account without authentication. Because refresh tokens are long-lived and self-renewing, a successful retrieval grants persistent, long-term access to the linked Google account well beyond any single session. A publicly available exploit exists per WPScan, though EPSS remains low (0.16%, 6th percentile), suggesting exploitation is not yet widespread.
URI fragment leakage in guzzlehttp/guzzle's RedirectMiddleware (versions before 7.15.1) exposes sensitive client-side data to unintended redirect destinations when the non-default `allow_redirects.referer` option is explicitly enabled. An attacker who controls a same-scheme redirect target can harvest one-time login tokens, OAuth state values, or access tokens embedded in URI fragments from the Referer header included in the redirected request. No public exploit has been identified at time of analysis, but the CVSS 4.0 score of 8.2 with AC:H and AT:P accurately reflects the real-world complexity - exploitation requires three simultaneous non-trivial conditions to align.
Heap out-of-bounds read in FreeRDP's glyph cache subsystem (versions <= 3.28.0) allows a malicious or compromised RDP server to crash any connecting FreeRDP client by sending a GLYPH_FRAGMENT_ADD update with a server-controlled declared fragment size that exceeds the actual received buffer. The vulnerability exists because update_process_glyph_fragments() and glyph_cache_fragment_put() in libfreerdp/cache/glyph.c read a one-byte declared size and proceed to allocate and copy that many bytes without first validating that the declared size fits within the remaining data in the received packet. No public exploit or CISA KEV listing has been identified at time of analysis, but the CVSS 4.0 score of 8.7 with AV:N/AC:L/PR:N reflects trivial remote exploitation requiring only a client connection to a rogue server.
Authentication bypass in Better Auth before 1.6.11 stems from insecure cryptographic defaults in the legacy oidcProvider and mcp plugins, which advertise the 'none' signing algorithm in OIDC discovery and accept plain PKCE by default. Relying parties whose JWT libraries negotiate the algorithm from discovery metadata without pinning can be tricked into accepting unsigned ID tokens, while exposed authorization URLs allow interception of codes because plain PKCE offers no protection. Reported by VulnCheck with a vendor patch available; there is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Cluster attribution spoofing in Wazuh 5.0.0-beta1 and beta2 allows an authenticated enrolled agent to forge wazuh.cluster.name and cluster_node values in inventory-sync FlatBuffer Start messages, because the server validates only the agentid against the enrolled identity while accepting arbitrary cluster metadata fields from the caller. In shared-indexer multi-cluster deployments where numeric agent IDs collide across clusters, a malicious agent can inject inventory and vulnerability documents into a foreign cluster's namespace, corrupting that cluster's security posture data. No public exploit has been identified at time of analysis; exploitation is constrained to pre-release beta deployments and requires an already-enrolled agent, substantially limiting real-world exposure.
Cluster token exposure in ArcadeDB before 26.7.2 enables any authenticated user to escalate privileges to root-level administrative control. The GET /api/v1/server management endpoint returns the arcadedb.ha.clusterToken value in cleartext, which an attacker can replay via the X-ArcadeDB-Cluster-Token and X-ArcadeDB-Forwarded-User HTTP headers to impersonate the root account. This two-stage privilege escalation grants full administrative capabilities including user creation, arbitrary database operations, and server shutdown - representing a near-total system compromise for any multi-tenant or shared ArcadeDB deployment. No public exploit has been identified at time of analysis and this CVE is not listed in the CISA KEV catalog, but the exploitation path is mechanically trivial once credentials are obtained.
Uncontrolled Recursion in Apache Lucy, a retired full-text search library, enables remote unauthenticated attackers to crash the service via a crafted input, resulting in a complete denial of availability across all versions ever released. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) confirms low-complexity, unauthenticated network exploitation with no confidentiality or integrity impact. No patch exists or will be issued by the Apache Software Foundation, as the project is officially retired; EPSS is low at 0.15% (5th percentile) and no active exploitation (CISA KEV) has been identified at time of analysis.
SQL injection in the Ajax Load More WordPress plugin before 8.0.1 lets unauthenticated attackers inject into an unsanitised parameter used in a database query, enabling time-based blind extraction of sensitive data such as user credentials and secrets. Reported by WPScan with publicly available exploit detail and a vendor patch in 8.0.1; scored CVSS 9.1 with an unauthenticated network vector. EPSS is low (0.19%, 9th percentile), indicating limited observed exploitation despite the critical rating.
Password-protected block content in the Passster WordPress plugin (all versions before 4.3.6) is rendered into the public HTTP response body before the server evaluates the password check, making the gate purely cosmetic. Unauthenticated remote users can retrieve protected content by inspecting the raw response - no password required. A public proof-of-concept exploit is available via WPScan, and the CVSS 3.1 score of 7.5 (AV:N/AC:L/PR:N/UI:N) confirms trivial remote exploitation with full confidentiality impact, though EPSS at 0.16% (5th percentile) and no CISA KEV listing indicate exploitation has not yet become widespread or automated.
Category-locked content in the Passster WordPress plugin (all versions before 4.3.6) is fully exposed through the native WordPress REST API, bypassing the plugin's access controls entirely. Unauthenticated remote users can retrieve the title, full body, and excerpt of any post that site owners intended to restrict using Passster's category-based protection. A publicly available exploit exists per WPScan; no CISA KEV listing and a low EPSS of 0.16% (5th percentile) indicate limited observed in-the-wild exploitation so far, but the trivial exploitation conditions make this an immediate upgrade priority for any site relying on Passster to gate sensitive content.
Unauthenticated content disclosure in the Passster WordPress plugin (versions before 4.3.6) allows any remote user to retrieve the full content of draft, private, and pending posts via a REST API endpoint that skips post-status validation. The flaw is conditional on the target site having a captcha provider configured, which is the typical deployment mode for Passster installations. Publicly available exploit code exists per WPScan reporting, though EPSS sits at only 0.16% (5th percentile), suggesting exploitation remains targeted rather than widespread. No CISA KEV listing has been issued.
Account takeover in the Membership Plugin - Kadence Memberships (formerly Restrict Content) for WordPress affects all versions through 4.0.0 via password-reset link poisoning. The legacy lost-password handler trusts an attacker-controlled rc_redirect POST value, so an unauthenticated attacker can trigger a reset email for any account (including administrators) whose reset link points at an attacker-controlled host carrying a valid key/login; when the victim clicks it, the reset key leaks and can be replayed to seize the account. No public exploit identified at time of analysis, and the flaw is not in CISA KEV, but Wordfence-confirmed root cause and a straightforward primitive make this a high-priority patch (CVSS 9.3).
Remote code execution as root is achievable against H3C NX15 firmware V100R017 via the `/api/esps` Web API endpoint, which exposes the `service.add` function without adequate access controls (CWE-749). Exploitation requires high-privilege authentication, but a post-authentication proof-of-concept script (`postauth_service_add_rce.py`) is publicly available on GitHub, demonstrating a complete root RCE chain. No vendor patch has been identified at time of analysis; no active exploitation is confirmed in CISA KEV.
Out-of-bounds read in S2OPC Toolkit 1.7.3's RepublishResponse message handler enables unauthenticated remote attackers to crash the OPC UA service via a crafted network message, resulting in denial of service. The vulnerable code paths span the subscription publish service layer (msg_subscription_publish_bs.c, msg_subscription_publish_ack_bs.c) and the common encoder module (sopc_encoder.c). No public exploit code or CISA KEV listing exists at time of analysis, but the CVSS:3.1 AV:N/AC:L/PR:N/UI:N vector indicates low-barrier remote exploitation requiring no authentication against reachable OPC UA endpoints.
Incorrect buffer size calculation (CWE-131) in an unidentified Linux distribution package tracked by both Ubuntu and Red Hat enables local, user-interaction-triggered exploitation with high confidentiality, integrity, and availability impact, yielding a CVSS base score of 7.8. The local attack vector combined with a user-interaction requirement (AV:L/UI:R/PR:N) is consistent with a malicious file parsing scenario, where a user opens a crafted input triggering the buffer miscalculation. No public exploit has been identified at time of analysis, and no KEV listing is present; however, the full C:H/I:H/A:H impact triad indicates potential for memory corruption leading to arbitrary code execution.
Improper TLS certificate validation in multiple Lenovo XClarity Orchestrator (LXCO) 2.2.0 microservices exposes sensitive management communications to interception by an adjacent network attacker capable of positioning themselves for a machine-in-the-middle attack. The flaw (CWE-295) allows the attacker to bypass HTTPS trust enforcement under unspecified triggering circumstances, potentially capturing credentials, tokens, or orchestration data exchanged between LXCO microservices. No public exploit code or CISA KEV listing exists at time of analysis; Lenovo has released a patch via advisory HT509976.
Unauthenticated OAuth2 access-token theft in Flowise (npm/flowise <= 3.1.2) stems from the token-refresh endpoint POST /api/v1/oauth2-credential/refresh/:credentialId being listed in WHITELIST_URLS, so it bypasses authentication entirely. Any remote party who knows or guesses a credential ID can force the server to decrypt the stored OAuth2 credential, refresh it against the provider using the victim's client secret, and receive the fresh access_token directly in the response body. No public exploit code has been identified, but the researcher (Shinobi Security) validated the missing-auth behavior in Docker, and a vendor-released patch is available in 3.1.3.
Out-of-bounds read in SSSD's PAM responder allows a local low-privileged attacker to crash the SSSD process and disclose sensitive memory contents by sending a crafted protocol v1 authentication request. Affected systems span all major Red Hat Enterprise Linux releases (6 through 10) and OpenShift Container Platform 4, representing a broad footprint in enterprise Linux environments. No active exploitation is confirmed (not listed in CISA KEV), and the EPSS score of 0.14% at the 3rd percentile reflects a very low observed exploitation probability at time of analysis.
Broken access control in Flowise's GET /api/v1/upsert-history API endpoint exposes the entire server-wide upsert history - exceeding 100MB per response - to any authenticated user, leaking sensitive infrastructure credentials including Qdrant server URLs, collection names, and vector pipeline configuration across all tenants and workspaces. The vulnerability is confirmed in flowise <= 3.1.2 and publicly documented in GHSA-fr6g-7cq8-fg82 with a working curl-based proof-of-concept, meaning any account holder on a multi-tenant deployment can harvest cross-tenant vector store configuration for reconnaissance or targeted follow-on attacks against exposed backends. Vendor-released patch flowise@3.1.3 is confirmed available and addresses missing workspace-scoping enforcement across multiple API controllers.
Remote code execution, data tampering, denial of service, and information disclosure are possible through vulnerabilities in NVIDIA Dynamo for Linux examples and recipes, affecting all versions through v1.1.0. The root cause is CWE-1357 (Relies on Insufficiently Trustworthy Component), meaning the examples or recipes bundle or reference a dependency or component without adequate integrity or trust verification, enabling an attacker to exploit that trust boundary over a network. No public exploit code exists and no active exploitation has been confirmed; EPSS places probability at 0.36% (29th percentile) and SSVC confirms exploitation status as none with a non-automatable attack path, suggesting low near-term weaponization risk despite the high CVSS base score.
Server-side request forgery in NVIDIA Dynamo's Rust multimodal media fetcher (Linux, versions through v1.1.0) allows unauthenticated remote attackers to coerce the server into issuing arbitrary HTTP requests to attacker-controlled destinations. A successful exploit can expose sensitive internal network resources, cloud metadata endpoints (e.g., IMDS at 169.254.169.254), or internal API responses, resulting in high-confidence information disclosure. No public exploit code or CISA KEV listing exists at time of analysis.
Server-side request forgery via DNS rebinding in NVIDIA Dynamo's multimodal media fetcher exposes internal network resources to remote unauthenticated attackers. All Dynamo releases from version 0 through v1.1.0 on Linux are affected. A successful exploit allows an attacker to manipulate the media fetcher into issuing HTTP requests to internal services, leading to high-confidence information disclosure - including potentially cloud metadata endpoints, internal APIs, or adjacent microservices. No public exploit code and no CISA KEV listing have been identified at time of analysis, though the CVSS 7.5 rating and unauthenticated network vector make this a meaningful risk in exposed deployments.
Server-side request forgery in NVIDIA Dynamo's multimodal media fetcher (Linux, versions through v1.1.0) allows unauthenticated remote attackers to issue arbitrary server-side HTTP requests by supplying malicious URLs as media inputs during inference. The CVSS 3.1 vector confirms network-accessible, zero-authentication exploitation with high confidentiality impact, scoring 7.5. No active exploitation or public exploit code has been identified at time of analysis, but SSRF in cloud-hosted AI inference infrastructure carries meaningful risk due to cloud metadata service exposure.
Server-side request forgery in NVIDIA Dynamo for Linux (all versions through v1.1.0) allows unauthenticated remote attackers to force the inference server to issue arbitrary HTTP requests by embedding a crafted URL inside a multimodal inference request payload. Successful exploitation exposes internal network resources reachable from the Dynamo host, producing high-severity information disclosure without requiring any credentials or user interaction. No public exploit code or CISA KEV listing has been identified at time of analysis, though the PR:N/AC:L attack surface on AI serving endpoints that may be network-exposed warrants prompt remediation.
Server-side request forgery in NVIDIA Dynamo for Linux (versions 0 through v1.1.0) enables unauthenticated remote attackers to cause the server to issue arbitrary backend HTTP requests. The CVSS:3.1 vector (AV:N/AC:L/PR:N/UI:N) confirms network-exploitable with no authentication or user interaction required, making this accessible to any attacker who can reach the Dynamo service. Successful exploitation leads to confidentiality impact - likely exposure of internal services, cloud instance metadata endpoints, or internal API responses - with no public exploit or CISA KEV listing identified at time of analysis.
Server-side request forgery in NVIDIA Dynamo for Linux (versions through v1.1.0) allows unauthenticated remote attackers to read arbitrary local files by embedding a crafted local path inside a multimodal inference request. The Dynamo serving layer fails to restrict the path to an allowed directory, causing the server to resolve and return content from restricted filesystem locations, leading to high-confidentiality information disclosure. No public exploit code or CISA KEV listing has been identified at time of analysis; however, the low attack complexity and lack of authentication requirements make this straightforward to exploit against any exposed Dynamo endpoint.
Path traversal in NVIDIA Dynamo's image loading component on Linux enables unauthenticated remote attackers to read arbitrary files outside the intended restricted directory, resulting in high-severity information disclosure. All releases from version 0 through v1.0.0 are affected, per EUVD-2026-52804 and the NVIDIA product security advisory. No public exploit code or active exploitation has been identified at time of analysis, though the CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates low-complexity, authentication-free exploitation against any network-exposed instance.
Hash collision exploitation in NVIDIA Dynamo's multimodal embedding cache on Linux allows unauthenticated remote attackers to corrupt cached inference data by submitting specially crafted images. The cache fails to incorporate image dimensions into its hash function, meaning two images with identical pixel byte sequences but different spatial dimensions resolve to the same cache key, causing the wrong embedding to be served for subsequent requests. No public exploit code has been identified and this vulnerability is not listed in the CISA KEV catalog, but the CVSS score of 7.5 with no authentication requirement (PR:N) elevates its priority in deployments where the inference API is network-accessible.
Out-of-bounds write in the multimodal serving topology of NVIDIA Dynamo for Linux allows remote unauthenticated attackers to corrupt memory, with a rated 9.8 CVSS potentially enabling remote code execution, privilege escalation, data tampering, information disclosure, and denial of service. NVIDIA (the reporting vendor) rates it critical with a network-reachable, no-privilege, no-interaction vector. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, so the score reflects potential rather than observed impact.
Path traversal in NVIDIA Triton Inference Server's MLflow plugin allows a low-privileged local user to read, write, or modify files outside the designated model repository by embedding traversal sequences in a model name parameter. All Linux deployments of Triton Inference Server through version 26.02 are affected. No active exploitation has been confirmed (not listed in CISA KEV), EPSS is 0.16% (6th percentile), and SSVC rates exploitation status as none - indicating this is a real but currently low-observed-risk vulnerability that warrants patching on a standard cadence rather than emergency response.
Flowise's patch for CVE-2025-8943 is fully bypassed in versions up to and including 3.1.2, allowing unauthenticated remote code execution on default deployments via the npm_config_yes environment variable. The prior mitigation blocked the -y and --yes flags on npx and denied four specific environment variable names by exact string match, but npm natively reads its configuration from any npm_config_* prefixed variable, making npm_config_yes=true semantically equivalent to --yes. Any attacker who can submit a Custom MCP stdio server configuration - which requires no authentication on default Flowise deployments - can force npx to auto-install and execute an arbitrary package as the Flowise server process. No public exploit code has been identified at time of analysis, though the bypass technique is fully documented in the public GHSA advisory GHSA-xc48-889x-5qmw, making independent weaponization trivial.
Credential theft via agent impersonation in Veeam Service Provider Console (VSPC) allows a remote, unauthenticated attacker to masquerade as a legitimately managed backup agent and harvest that agent's credentials. Because VSPC is the multi-tenant management plane MSPs use to orchestrate backups across customer estates, captured agent credentials give an attacker a foothold to pivot into managed endpoints. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but the vendor rates it critical (9.5) and CWE-288 identifies an authentication-bypass root cause.
Memory exhaustion in Veeam Service Provider Console (VSPC) allows unauthenticated remote attackers to deplete host memory and cause a denial of service, with no authentication or user interaction required. The CVSS 4.0 score of 8.7 reflects the network-accessible, zero-prerequisite nature of exploitation (AV:N/AC:L/AT:N/PR:N/UI:N) with high availability impact confined to the vulnerable system. No public exploit code and no CISA KEV listing have been identified at time of analysis, but the low exploitation barrier makes any internet-exposed VSPC instance a realistic target.
Qualcomm Snapdragon chipsets fail to verify the consistency of UE security capabilities against those replayed by the network during 3GPP cellular security mode negotiation, enabling a rogue base station operator to force downgraded cryptographic algorithm selection on unpatched devices. The flaw resides in the cellular modem firmware stack and affects all Snapdragon product lines per available CPE data, with no minimum version boundary published. Exploitation yields high confidentiality impact - a sophisticated attacker with radio interception equipment can potentially decrypt cellular communications. No public exploit code and no CISA KEV listing have been identified at time of analysis, though the underlying attack class (security capability bidding-down) is well-documented in cellular security research.
pardus-image-writer before 1.0.4, developed by TÜBİTAK BİLGEM Software Technologies Research Institute for Turkey's national Pardus Linux distribution, permits external control of file name or path (CWE-73), enabling a locally authenticated attacker to redirect file operations outside their intended scope and remove important client functionality. The CVSS vector (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H, score 7.1) confirms that standard user privileges and no interaction from other users are required, with high integrity and availability impact but no confidentiality impact. No public exploit code or active exploitation has been identified at time of analysis; this is a Turkish CERT (USOM)-reported vulnerability with a confirmed fix at version 1.0.4.
Unauthenticated remote denial-of-service in Eclipse Milo 0.6.0-1.1.4 allows any network-accessible client to exhaust the OPC UA server's off-heap direct memory pool by repeatedly sending incomplete UASC message chunks and disconnecting before message assembly completes. The UASC server-side asymmetric handler and ChunkDecoder fail to invoke ReferenceCountUtil.safeRelease() on retained Netty ByteBuf objects when the channel lifecycle ends, causing unbounded off-heap memory accumulation. No authentication is required and no special server configuration is necessary; the fix commit is publicly available on GitHub, serving as an effective blueprint for exploitation, though no standalone POC tool or CISA KEV listing has been identified at time of analysis.
Password recovery in Eclipse Milo (the open-source OPC UA SDK for Java) versions 0.6.0 through 1.1.4 allows an on-path attacker to break username-token confidentiality via a Bleichenbacher-style padding oracle. The server returns distinguishable error responses for invalid RSA PKCS#1 v1.5 padding versus other authentication failures during username-token processing, so an attacker who captures a victim's Basic128Rsa15-encrypted username token can send repeated unauthenticated ActivateSession requests to recover the cleartext password and then authenticate as the victim. No public exploit identified at time of analysis and it is not listed in CISA KEV; the weakness and its upstream fix are confirmed by the Eclipse Foundation.
Session hijacking is possible in HUMANIST Digital Human Resources (versions 26.0 through before 26.1) due to sensitive session tokens being transmitted as GET request query string parameters. Exposure occurs through server access logs, browser history, and HTTP Referer headers leaking to downstream systems. No public exploit code has been identified at time of analysis, and no CISA KEV listing exists, but the CVSS integrity and confidentiality impact ratings are both High, reflecting full session takeover potential.
Sensitive-data exposure in Bilin Software's HUMANIST Digital Human Resources (versions 26.0 up to but not including 26.1) stems from a cryptographic key embedded directly in the application binary, letting attackers recover the same static key from any deployment and abuse it against protected data. Because the key is identical across all installations, its extraction undermines confidentiality and integrity of anything it protects. No public exploit identified at time of analysis, and the flaw was reported through Turkey's national CSIRT (TR-CERT).
Hard-coded RSA private key exposure in GeoVision GV-AS1620 (GV-Cloud) access-control appliances lets remote attackers decrypt and forge the device's HTTPS traffic. The firmware ships an embedded, static RSA private key used by the built-in Lighttpd web server for TLS termination, so anyone who extracts it from one device can passively decrypt or actively impersonate the management interface of every device sharing that key. No public exploit identified at time of analysis, but the shared-secret nature makes the flaw broadly reusable once the key is recovered.
Hard-coded RSA private key exposure in the GeoVision GV-AS1620 (AS Manager) access-control device lets attackers who extract the firmware-embedded key decrypt and forge the Lighttpd TLS session used for the device's HTTPS management interface. Because the key is static and shared across all units of the same firmware, a single extraction compromises every deployed device, enabling passive traffic decryption and active server impersonation. No public exploit is identified at time of analysis, and the issue is not listed in CISA KEV.
Kernel memory corruption in the Linux kernel SCTP stack allows a remote peer to trigger a use-after-free during ASCONF DEL-IP processing, corrupting an association's transport list and leaving primary_path/active_path pointing at freed memory. The flaw affects the SCTP dynamic address reconfiguration (ASCONF) path across a wide range of kernel versions and, given kernel-level impact, can lead to denial of service and potentially privilege escalation or code execution. Despite the 9.8 CVSS and 'Information Disclosure' tag, there is no public exploit identified at time of analysis and EPSS is low (0.16%), reflecting the SCTP/ASCONF-specific conditions required.
Race condition in the Linux kernel's KVM nVMX (nested VMX) subsystem allows a low-privileged local attacker to trigger a use-after-free via shadow VMCS teardown, with potential for full hypervisor compromise. The flaw arises because free_nested() releases the shadow VMCS page while vmcs01 still holds a dangling pointer; if the vCPU migrates to another physical CPU before the pointer is cleared, __loaded_vmcs_clear() executes VMCLEAR against the freed page, corrupting kernel memory. No public exploit code exists and no active exploitation is confirmed (EPSS 0.16%, 5th percentile), but the S:C scope change in the CVSS vector and the C:H/I:H/A:H impact triad indicate this could enable a guest-to-host escape under the right conditions.
Shadow MMU ordering flaw in the Linux kernel KVM x86 subsystem allows a low-privileged guest process to corrupt the hypervisor's page table state by triggering invalid root population during shadow page reclamation. Kernels from 5.9 through multiple unpatched stable branches permit child shadow pages to be created under an invalidated parent root, violating a core MMU invariant and potentially enabling guest-to-host privilege escalation. No public exploit has been identified and EPSS is low (0.16%), but the confirmed scope change to the host hypervisor makes this a high-priority patch for any KVM-based multi-tenant or cloud virtualization environment.
Out-of-bounds read in open62541 1.5.5 allows a malicious OPC UA server to crash connecting clients via a crafted namespace array response. The flaw resides in the client-side connection handler responseReadNamespacesArray() in src/client/ua_client_connect.c, triggered during the namespace discovery phase of the OPC UA session establishment. With a CVSS availability impact of High and no privileges required on the attacker side, the practical effect is a remotely-induced denial of service against any open62541-based OPC UA client that connects to an attacker-controlled server. No public exploit identified at time of analysis.
Microsoft Edge for Android exposes device file contents to remote attackers through an external file path control flaw (CWE-73), enabling information disclosure across a scope boundary. The CVSS vector (S:C, C:H) confirms the vulnerability crosses from the browser sandbox into the broader Android file system or other protected resources. No public exploit code exists and an official vendor fix is available; exploitation requires user interaction, making this a meaningful but not critical-priority risk for most deployments.
External file path control in Microsoft Edge for Android (versions below 151.0.4129.59) allows a local low-privileged attacker to disclose sensitive information stored on the device. Rooted in CWE-73, the flaw permits attacker-controlled input to dictate file name or path resolution within the browser, potentially exposing files outside the intended access scope. No public exploit identified at time of analysis, and SSVC confirms no known exploitation; however, the CVSS C:H and I:H ratings suggest the path control primitive may extend beyond read-only disclosure.
Origin validation bypass in Microsoft Edge (Chromium-based) enables a remote, unauthenticated attacker to circumvent Same-Origin Policy protections, resulting in unauthorized cross-origin access to sensitive data. The flaw (CWE-346) affects all versions of Chromium-based Edge and carries a vendor CVSS of 8.1 with both high confidentiality and high integrity impact - the latter is notable given the description characterizes this as an information disclosure issue, a discrepancy that warrants verification against the MSRC advisory. No public exploit code exists and the vulnerability is not listed in CISA KEV; Microsoft has released an official patch.
JSON-LD signature validation in Misskey's ActivityPub federation layer accepts fraudulent federated activities due to a TOCTOU flaw where the JSON-LD parsing context used during signature verification is not shared with the context used during subsequent message processing. Affected are all self-hosted Misskey instances running versions 12.37.0 through 2026.5.3. A remote, unauthenticated attacker operating or spoofing a federated server can craft payloads that pass signature checks yet resolve to malicious content during processing, resulting in high integrity impact across the instance and potentially propagating to federated peers; no public exploit or CISA KEV listing has been identified at time of analysis.
Signature validation bypass in Misskey (versions 12.37.0 through prior to 2026.5.4) allows an attacker to have spoofed ActivityPub activities accepted as authentic. The flaw resides in the JSON-LD signature validation and compaction logic (CWE-347), enabling forgery of federated actions such as posts or actions attributed to other actors/instances. The CVSS 4.0 base score is 9.2 (Critical) with a network, unauthenticated, low-complexity vector emphasizing integrity impact; no public exploit has been identified at time of analysis, and it is not listed in CISA KEV.
PKCS#7 EnvelopedData decryption in the Python cryptography library (versions 44.0.0-49.x) leaks a Bleichenbacher oracle through four distinguishable error messages and timing side-channels during RSA PKCS#1 v1.5 key unwrapping, exposing the exact recovered plaintext length in one case. An attacker who can submit crafted EnvelopedData to an auto-decrypting service - such as an S/MIME gateway or mail filter that reflects outcomes at high volume - can adaptively recover the content-encryption key and decrypt intercepted messages. No public exploit has been identified at time of analysis, and exploitation requires very specific deployment conditions; the fix in version 50.0.0 applies RFC 3218 indistinguishability by substituting a random key on any failure.
Host confusion in GuzzleHttp Guzzle before 7.15.2 and 8.0.1 allows remote attackers who can influence a fetched URI to bypass application-level host validation and reach network hosts the application intended to block, including loopback and internal addresses. The divergence occurs because PHP's filter_var() and Guzzle's own host checks operate on the literal URI text while libcurl independently percent-decodes and IDNA-maps the authority before resolving and connecting, meaning the application and transport disagree on which host is being contacted. No public exploit has been identified and the vulnerability is absent from the CISA KEV catalog, but any application that implements SSRF mitigations via URI host inspection before passing a user-supplied URL to Guzzle is directly undermined.
Blind SQL injection in Shlink's tag statistics REST endpoint allows any API key holder to extract sensitive data from the underlying database across all tenants. The unvalidated `direction` value of the `orderBy` query parameter flows unsanitized into a Doctrine QueryBuilder ORDER BY clause, enabling time-based, boolean-oracle, and error-based extraction of long URLs, visitor records, IP addresses, geolocation data, user agents, and hashed API key secrets. A public proof-of-concept exploit is available on GitHub, no public exploit identified at time of analysis as confirmed actively exploited, but the low barrier to exploitation - any valid API key suffices - makes this a genuine remediation priority for Shlink operators.
Uncontrolled decompression in Apache NiFi 1.5.0 through 2.10.0 exposes the REST API to unauthenticated denial-of-service attacks via crafted gzip payloads. The Jersey encoding filter enforces its configurable size limit against the compressed form of the request body rather than the decompressed output, enabling a classic zip-bomb condition that can exhaust JVM heap memory. No public exploit has been identified at time of analysis, but the CVSS 4.0 supplemental metadata flags the attack as automatable (AU:Y) with Amber utility, indicating meaningful real-world risk against organizations with network-accessible NiFi REST API endpoints.
Memory exhaustion via malformed binary attachment packets in the socket.io-parser npm library allows unauthenticated remote attackers to crash or hang Socket.IO servers. By sending crafted packets that declare a large number of pending binary attachments, an attacker causes the server's Decoder to allocate and hold buffers indefinitely, exhausting Node.js heap memory. The vendor advisory (GHSA-2m8v-j782-fhvr) confirms the impact and vendor-released fixed versions are available; no public exploit code or CISA KEV listing has been identified at time of analysis.
Injection vulnerability in GL-iNet GL-MT3000 (Beryl AX) firmware through version 4.4.5 exposes the plugins.set_config function via /cgi-bin/glc to remote exploitation with no authentication or user interaction required per the CVSS 4.0 vector. Successful exploitation yields high confidentiality, integrity, and availability impact on the device, consistent with OS command or argument injection against the native plugin handler. A proof-of-concept exploit is publicly available on GitHub and the vendor has confirmed the vulnerability, though no patch has been released at time of analysis.
Local privilege escalation in Dell Monitor Driver exploits a symlink (link-following) flaw to allow a low-privileged local attacker to elevate to higher system privileges, achieving full confidentiality, integrity, and availability impact on the host. The vendor has released a patch via Dell Security Advisory DSA-2026-295, and no public exploit code has been identified at time of analysis. EPSS rates exploitation probability at 0.11% (2nd percentile), and SSVC classifies exploitation as none and automatable as no - consistent with the local-only attack vector and the absence of CISA KEV listing.
HttpTransferCache key collision in Angular's Server-Side Rendering subsystem enables cache poisoning by exploiting identical serialization of scalar comma-separated query parameters and semantically distinct repeated query parameters against the same endpoint. Angular SSR applications using client-side hydration across versions 20.x, 21.x, and 22.x - and 19.x with no available patch - are at risk of having security-sensitive HttpClient responses silently replaced by earlier attacker-influenced cached responses, bypassing trusted backend authorization calls entirely. Vendor patches 22.0.2, 21.2.19, and 20.3.27 are confirmed available; no public exploit code and no CISA KEV listing exist at time of analysis.
Information disclosure in SiYuan (a personal knowledge-management/note-taking application) before v3.7.3 lets anonymous readers or low-privilege publish RoleReader tokens read the full rendered content of documents that were explicitly marked publish-disabled. The getHeadingDeleteTransaction, getHeadingLevelTransaction, and getHeadingInsertTransaction endpoints return rendered block DOM without enforcing publish-access checks, so supplying a target heading block ID leaks restricted content. Reported by VulnCheck with a vendor patch available; no public exploit identified at time of analysis, and this is not listed in CISA KEV.
Uncontrolled recursion in Bouncy Castle for Java's lazy ASN.1 parser enables remote unauthenticated denial of service across all three library release lines (bc-java, bc-lts-java, and bc-fja FIPS). When a LazyEncodedSequence is forced during tree traversal, it resets the nesting-depth guard to its configured maximum instead of continuing with the remaining depth budget, allowing crafted deeply-nested ASN.1 structures to bypass StreamUtil's recursion limit and trigger a StackOverflowError. No public exploit has been identified at time of analysis, but any Java application accepting externally-supplied ASN.1 data - TLS certificates, CMS signatures, PKCS structures - is potentially exposed without authentication.
RSA PKCS#1 v1.5 signature forgery is possible in Bouncy Castle for Java (bc-java before 1.85, bc-lts-java before 2.73.12) when the DigestInfo encoding omits the NULL AlgorithmIdentifier parameter. The off-by-two bytes in the RSADigestSigner comparison loop allows any forged signature whose DigestInfo matches all bytes except the final two of the message hash to pass verification as valid, achieving a high-integrity bypass. No public exploit has been identified at time of analysis, but the public patch commit includes a step-by-step test demonstrating the exact forgery technique, substantially lowering the bar to exploitation.
Heap exhaustion via uncontrolled memory allocation in Bouncy Castle for Java's MLS wire decoder allows remote unauthenticated attackers to crash any application using the bc-java MLS module. The MLSInputStream.readOpaque() method decodes an attacker-supplied Varint length field (up to 0x3FFFFFFF, approximately 1 GiB) and allocates that buffer before verifying the input stream actually contains that many bytes; a handful of concurrent few-byte crafted messages can exhaust the JVM heap. No public exploit has been identified at time of analysis and CISA KEV listing is absent, though the attack is trivially constructable from the published patch and regression test.
OpenPGP AEAD decryption in Bouncy Castle for Java silently bypasses the final authentication tag when plaintext is an exact multiple of the AEAD chunk length, allowing an attacker who can tamper with ciphertext to strip trailing plaintext chunks and have the truncated message accepted as cryptographically authentic. Affected libraries span bc-java before 1.85, bc-lts-java before 2.73.12, and all three active BC-FJA FIPS series before their respective bcpg-fips 1.0.13, 2.0.13, and 2.1.13 releases. No public exploit has been identified at time of analysis and this CVE is not listed in CISA KEV, but the CVSS 4.0 score of 8.7 (Integrity: High) reflects a complete and silent bypass of AEAD integrity guarantees for chunk-aligned messages with no downstream exception or warning.
IESEngine in Bouncy Castle for Java allows cross-message MAC forgery when stream mode is used with static key pairs, affecting bc-java before 1.85 and bc-lts-java before 2.73.12. The flaw stems from a length-dependent KDF output split: in the static-key path (no ephemeral V component), the MAC key K2 was placed at a byte offset equal to the message length after the keystream K1, so an observer of one known-plaintext encryption can recover K2 and forge valid ciphertext-plus-tag pairs for shorter messages. No public exploit beyond the vendor's own proof-of-concept regression test exists, and no CISA KEV listing is present at time of analysis.
Cross-nonce AEAD forgery in Bouncy Castle for Java's KCCMBlockCipher (DSTU 7624 CCM mode) allows an attacker with chosen-plaintext oracle access to forge valid authenticated ciphertext under an un-queried nonce when no associated authenticated data is present. All bc-java releases before 1.85 and bc-lts-java releases before 2.73.12 are affected. The G1 initialization block - which binds the nonce into the MAC under the DSTU 7624:2014 standard - was conditionally skipped when no AAD bytes were supplied, leaving the authentication tag independent of the nonce and breaking the core AEAD security guarantee. No public exploit has been independently released and this vulnerability is not listed in CISA KEV, though the fix commits include a working regression test that fully demonstrates the forgery technique.
CMS AuthEnvelopedData decryption in Bouncy Castle for Java fails to enforce a minimum AEAD authentication tag length, allowing a network attacker to supply a crafted CMS message carrying a truncated AES-GCM/CCM ICV (e.g., 32 bits instead of the standard 128 bits), effectively reducing the authentication space to the point where tag forgery becomes computationally feasible. Affected are bc-java before 1.85, bc-lts-java before 2.73.12, and all bc-fja (FIPS) 1.0.x/2.0.x/2.1.x series before their respective .12 patch releases. No public exploit or CISA KEV listing has been identified at time of analysis, but the CVSS 4.0 score of 8.7 with VI:H reflects the high integrity impact of bypassing authenticated encryption guarantees.
Out-of-memory denial-of-service in Bouncy Castle for Java allows remote unauthenticated attackers to crash Java applications by submitting a crafted ASN.1 definite-length object with an inflated declared size. The ASN.1 parser in `DefiniteLengthInputStream.toByteArray()` allocated a full heap-sized byte array before reading any body bytes, meaning a few-byte header claiming a near-JVM-heap payload was sufficient to trigger OOM. All major Bouncy Castle release lines are affected - including the FIPS-certified BC-FJA variant - and a vendor patch is available; no public exploit code or CISA KEV listing exists at time of analysis.
CPU exhaustion in Bouncy Castle for Java allows remote attackers to cause denial of service by supplying X.500 distinguished name attribute values densely packed with RFC 4514 special characters or leading/trailing spaces. The root cause is a quadratic-time O(n²) escaping algorithm in `IETFUtils.valueToString()` that inserts backslashes into the buffer being actively scanned - triggerable through `X500Name.toString()`, `.equals()`, or `.hashCode()`, methods commonly invoked during TLS certificate and LDAP DN processing. No public exploit has been identified beyond the vendor's own regression test, and this vulnerability is not listed in CISA KEV, though the CVSS 4.0 score of 8.7 with AV:N/PR:N signals meaningful exposure for Internet-facing Java services.
Uncontrolled memory allocation in Bouncy Castle for Java's HSS public-key parser allows remote unauthenticated attackers to exhaust JVM heap memory by supplying a crafted public key with an arbitrarily large HSS level count (L value), causing denial of service during signature verification. All three product lines are affected: bc-java before 1.85, bc-lts-java before 2.73.12, and BC-FIPS (bc-fja) before 2.0.2/2.1.3 depending on series. No public exploit has been identified at time of analysis and no CISA KEV listing exists, but the AV:N/AC:L/PR:N attack profile and Bouncy Castle's ubiquity as a Java crypto dependency make this a credible availability risk for any service accepting external HSS/LMS key material.
CCMBlockCipher in Bouncy Castle for Java decrypts ciphertext directly into the caller-supplied output buffer before verifying the authentication tag, leaving unverified CTR-decrypted plaintext in memory when tag verification fails and violating NIST SP 800-38C §6.2. Every edition - bc-java before 1.85, bc-lts-java before 2.73.12, and BC-FJA across three active release lines (1.0.x, 2.0.x, 2.1.x) - is affected. Applications that reuse pooled byte buffers, log failure-path output, or otherwise expose the buffer on an authentication failure inadvertently become CTR decryption oracles, allowing attackers to submit forged ciphertexts and recover plaintext without possessing a valid authentication tag. No public exploit and no CISA KEV listing exist at time of analysis.
Certificate revocation-check bypass in the Bouncy Castle for Java (bc-java) PKIX provider allows a validly-signed OCSP response issued for one certificate to be accepted as proof-of-status for a different certificate, because the stapled response is not bound to the CertID of the certificate actually being checked. This means a revoked end-entity certificate can pass PKIXRevocationChecker validation when a 'good' OCSP response for another serial (e.g. the CA's) is supplied, defeating revocation enforcement in TLS/PKI clients that rely on OCSP stapling. Affected releases are bc-java before 1.85, bc-lts-java before 2.73.12, and BC-FJA (FIPS) before 2.0.2 and 2.1.3; no public exploit identified at time of analysis and it is not listed in CISA KEV.
Out-of-bounds read in MediaTek modem firmware across 19 chipsets enables remote denial of service when a User Equipment (UE) is connected to an attacker-controlled rogue base station. The flaw stems from a missing bounds check (CWE-125) in modem protocol processing, crashing or disrupting the modem without requiring any user interaction or device-side privileges. No active exploitation is confirmed (no CISA KEV listing), and EPSS probability is very low at 0.21% (11th percentile), consistent with SSVC's 'exploitation: none' status - though the attack is classified as automatable once rogue infrastructure is in place.
TLS hostname-verification bypass in the Bouncy Castle for Java JSSE provider (BCJSSE) ships the legacy certificate-CN fallback enabled by default, even though the vendor documentation states it is opt-in and gated behind the org.bouncycastle.jsse.client.checkCnFallback property. Affected are BC-Java before 1.85, BC-LTS before 2.73.12, and BC-FJA (FIPS) TLS module bctls-fips before 1.0.24, 2.0.24 and 2.1.24; a MITM-positioned attacker can present a SAN-less certificate whose Subject CN names the victim host and have it silently accepted, defeating name-constraint protections and enabling interception of TLS traffic (CWE-297). This carries a CVSS 4.0 base of 9.3, but there is no public exploit identified at time of analysis and it is not in CISA KEV.
Signature bypass in Bouncy Castle for Java allows any attacker-supplied content wrapped in a zero-signer CMS envelope to pass `CMSSignedData.verifySignatures()` without any valid cryptographic signature. The method iterates an empty signerInfos SET, falls through to a vacuous `return true`, and any application using it as its top-level authenticity check silently accepts unsigned attacker-controlled content as authenticated - a classic fail-open flaw (CWE-347). No public exploit has been identified at time of analysis and the vulnerability is not listed in CISA KEV, but the attack primitive is trivially constructible using any standard CMS/PKCS#7 library.
Bouncy Castle for Java's OpenPGP session-key decryption path re-exposes the Mister-Zuccherato adaptive-chosen-ciphertext oracle by failing to suppress the legacy CFB 'quick check' on the PKESK/session-key route, enabling an attacker with decryption oracle access to recover plaintext from SEIPD v1 encrypted messages. Affected are bc-java before 1.85, bc-lts-java before 2.73.12, and BC-FJA (bcpg-fips) across the 1.0.X, 2.0.X, and 2.1.X series - three distinct product lines used broadly in enterprise and open-source Java applications. No public exploit or CISA KEV listing has been identified at time of analysis; however, the attack technique is well-established in cryptographic literature dating to the Mister-Zuccherato paper.
Signature forgery via back-dated signingTime in Bouncy Castle's S/MIME validator allows an attacker holding a revoked or expired signing certificate to have that certificate accepted as valid by unpatched validators. The SignedMailValidator in bc-java before 1.85, bc-lts-java before 2.73.12, and all bc-fja (FIPS) lines before their respective 1.0.7/2.0.7/2.1.7 fixes unconditionally used the signer-asserted CMS signingTime attribute as the PKIX path-validation date, making certificate expiry and revocation checks bypassable. No public exploit or CISA KEV listing exists at time of analysis, but the flaw is architecturally straightforward to exploit by any party that holds or has previously held a Bouncy Castle-validated signing certificate.
CMS AuthenticatedData integrity verification in Bouncy Castle for Java is bypassable when authenticated attributes (authAttrs) are present, allowing an attacker to substitute arbitrary content while the recipient MAC check passes without error. Affected are bc-java before 1.85, bc-lts-java before 2.73.12, and BC-FJA across the 1.0.x, 2.0.x, and 2.1.x series - all widely deployed in Java enterprise and FIPS environments. The CVSS 4.0 vector (AV:N/AC:L/PR:N/UI:N/VI:H) reflects unauthenticated remote exploitation with high integrity impact; no public exploit or CISA KEV listing is confirmed at time of analysis.
OpenPGP inline-signature policy enforcement in Bouncy Castle for Java silently discards rejection exceptions, causing signatures that use prohibited weak hash algorithms (MD5, SHA-1, RIPEMD-160) or otherwise violate the configured OpenPGPPolicy to be reported as cryptographically valid. Affected are bc-java before 1.85 and bcpg-fips (bc-fja) before 2.0.13; the detached-signature and prefixed-signature verification paths are not affected - only the inline one-pass path. A vendor patch is available; no public exploit code has been identified at time of analysis, though the CVSS 4.0 score of 8.7 reflects a high integrity impact driven by the unauthenticated network vector.
CPU exhaustion in Bouncy Castle for Java's MLS (Messaging Layer Security) implementation allows a network attacker to trigger unbounded HKDF key-derivation iterations by supplying a crafted 32-bit generation counter in an MLS message. The hash-ratchet in GroupKeySet.get(int generation) advances one HKDF step per skipped generation without any upper bound, so a maximally crafted counter forces up to ~4.29 billion derivation steps on the receiving process. Scored CVSS 4.0 at 8.7 with High availability impact and no authentication prerequisites per vendor scoring; no public exploit code or KEV listing has been identified at time of analysis.
Unbounded recursion in Bouncy Castle's OER (Octet Encoding Rules) parser enables remote unauthenticated denial-of-service against any Java application processing IEEE 1609.2 V2X messages. Because the IEEE 1609.2 schema is cyclic - an Ieee1609Dot2Data structure can nest inside its own SignedData payload - a few kilobytes of crafted input drive the parser into unbounded recursive descent, terminating in a JVM StackOverflowError. Critically, parsing occurs before signature verification, so no authentication or trust relationship is needed to trigger the crash. No public exploit has been identified at time of analysis, but the patch commit exposes two additional heap-exhaustion vectors alongside the primary recursion flaw, all reachable from the same pre-verification code path.
Memory exhaustion denial-of-service in Bouncy Castle's DTLS implementation allows remote unauthenticated attackers to crash or degrade Java applications by sending crafted handshake messages with inflated 24-bit length fields. Affected are bc-java before 1.85, bc-lts-java before 2.73.12, and BC-FJA (bctls-fips) before 1.0.24, 2.0.24, or 2.1.24 depending on the deployed branch. The buffer allocation occurs pre-authentication during the DTLS handshake reassembly phase - before any signature or Finished verification - making this exploitable without credentials against any exposed DTLS endpoint. No public exploit code has been identified and the vulnerability is not listed in CISA KEV.
Memory exhaustion in Bouncy Castle for Java's OpenPGP parser enables unauthenticated remote denial of service via a crafted User Attribute subpacket with an oversized length header. All Java applications importing untrusted OpenPGP certificates using bc-java before 1.85, bc-lts-java before 2.73.12, or BC-FJA (FIPS) in affected series are vulnerable to pre-authentication JVM heap exhaustion. No KEV listing or public exploit has been confirmed at time of analysis, but the zero-complexity unauthenticated network attack vector and CVSS 4.0 score of 8.7 signal high operational priority for services that accept OpenPGP certificates from external sources.
Private key recovery in Bouncy Castle for Java (bc-java before 1.85, bc-lts-java before 2.73.12) affects the DH agreement code path, where a peer-supplied public value is exponentiated with the local private key without full range/subgroup validation. A malicious protocol peer can submit small-order or out-of-range Diffie-Hellman elements to mount a small-subgroup confinement attack and, when the local private key is static/reused, gradually recover it via CRT - enabling decryption and impersonation. No public exploit identified at time of analysis; the fix is a vendor-released patch and the vulnerability is not listed in CISA KEV.
Bouncy Castle for Java's BKS keystore implementation silently accepted legacy version 0/1 keystores that derive a critically weak 16-bit HMAC integrity key - brute-forceable offline in milliseconds against the 65,536-value keyspace - allowing an attacker who can supply or tamper with a keystore file to forge the integrity MAC, inject rogue trusted certificates, and have the manipulated keystore accepted without error. All bc-java releases before 1.85 and bc-lts-java releases before 2.73.12 are affected. No public exploit code has been identified and this vulnerability does not appear in the CISA KEV catalog at time of analysis.
Bouncy Castle for Java's BKS and UBER keystore implementation crashes with an OutOfMemoryError when loading a crafted keystore because heap allocation from stream-declared lengths occurs before the HMAC integrity check. Any application calling KeyStore.load() with attacker-controlled BKS or UBER keystore data is affected - bc-java before 1.85 and bc-lts-java before 2.73.12. A POC was submitted alongside the report, confirming that a file of just a few dozen bytes declaring Integer.MAX_VALUE-length fields is sufficient to exhaust JVM heap regardless of heap configuration or supplied password. No public exploit identified at time of analysis beyond the researcher's POC referenced in the patch commit.
Forced processor reset in NASA Core Flight System (cFS) v7.0.1 is achievable by supplying a crafted entry to the HS.AppMon_Tbl, exploited through the HS_MonitorApplications() function in the Health and Safety application module. The vulnerability targets embedded real-time flight software used in spacecraft, where an unplanned processor reset can have mission-critical consequences. A proof-of-concept exists per SSVC data, exploitation is rated automatable, and the EPSS score of 0.14% (4th percentile) suggests no widespread opportunistic scanning - consistent with narrow, targeted exploitation in aerospace operational contexts. No active CISA KEV listing has been confirmed.
Unauthenticated remote attackers can manipulate the CCSDS File Delivery Protocol (CFDP) metadata handler in NASA Core Flight System v7.0.1, specifically the CF_CFDP_RecvMd() function, to control the destination path where received file content is stored on the target system, resulting in high-impact information disclosure. A publicly available proof-of-concept exists per SSVC classification, making this exploitable without authentication or user interaction against any network-reachable cFS instance with the CF application enabled. Despite the availability of exploit code and network-accessible attack vector, the EPSS score of 0.14% (4th percentile) reflects the extremely limited real-world deployment footprint of this aerospace-domain platform.
Predictable API key generation in osTicket 1.18.3 lets remote attackers reconstruct valid staff API keys by exploiting weak MD5-based construction seeded with the request timestamp and client IP address (CWE-331). Because the key is derived from low-entropy, guessable inputs, an attacker who approximates the key creation window can brute-force the key space and gain API access without credentials. Rated CVSS 9.8 by the reporter; no public exploit is identified at time of analysis, though a technical disclosure write-up exists, and CISA SSVC lists exploitation as none but marks the flaw automatable with total technical impact.
Stack buffer over-read and stray one-byte NUL write in Zephyr RTOS's experimental OCPP 1.6 client allow a malicious or compromised OCPP central server - or an on-path attacker exploiting the commonly unencrypted ws:// transport - to crash a connected embedded device by sending a crafted WAMP RPC frame with an oversized uid or action field. The vulnerable helper extract_string_field() uses strncpy() without guaranteeing NUL-termination, causing a subsequent strchr() call to scan unbounded into adjacent stack memory; a secondary defect in extract_payload() compounds this on maximal-length frames. No active exploitation has been confirmed by CISA KEV, but SSVC classification indicates publicly available proof-of-concept code, and EPSS sits at a low 0.19% (10th percentile), consistent with a niche embedded RTOS attack surface.
Cleartext leakage of the HA cluster token in ArcadeDB's MCP get_server_settings tool allows any authenticated MCP user to escalate to full root-level server control in all versions before 26.7.3. The exposed arcadedb.ha.clusterToken can be replayed via the X-ArcadeDB-Cluster-Token and X-ArcadeDB-Forwarded-User HTTP headers to impersonate the root user, turning a low-privilege information disclosure into a complete server compromise. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog; however, the chained privilege escalation path significantly elevates real-world impact beyond the CWE-200 classification suggests.
Unauthenticated exposure of OAuth credentials in the Gallery for Google Photos WordPress plugin (all versions before 1.2.1) allows any remote attacker to retrieve the stored Google access and refresh tokens of the connected account without authentication. Because refresh tokens are long-lived and self-renewing, a successful retrieval grants persistent, long-term access to the linked Google account well beyond any single session. A publicly available exploit exists per WPScan, though EPSS remains low (0.16%, 6th percentile), suggesting exploitation is not yet widespread.
URI fragment leakage in guzzlehttp/guzzle's RedirectMiddleware (versions before 7.15.1) exposes sensitive client-side data to unintended redirect destinations when the non-default `allow_redirects.referer` option is explicitly enabled. An attacker who controls a same-scheme redirect target can harvest one-time login tokens, OAuth state values, or access tokens embedded in URI fragments from the Referer header included in the redirected request. No public exploit has been identified at time of analysis, but the CVSS 4.0 score of 8.2 with AC:H and AT:P accurately reflects the real-world complexity - exploitation requires three simultaneous non-trivial conditions to align.
Heap out-of-bounds read in FreeRDP's glyph cache subsystem (versions <= 3.28.0) allows a malicious or compromised RDP server to crash any connecting FreeRDP client by sending a GLYPH_FRAGMENT_ADD update with a server-controlled declared fragment size that exceeds the actual received buffer. The vulnerability exists because update_process_glyph_fragments() and glyph_cache_fragment_put() in libfreerdp/cache/glyph.c read a one-byte declared size and proceed to allocate and copy that many bytes without first validating that the declared size fits within the remaining data in the received packet. No public exploit or CISA KEV listing has been identified at time of analysis, but the CVSS 4.0 score of 8.7 with AV:N/AC:L/PR:N reflects trivial remote exploitation requiring only a client connection to a rogue server.
Authentication bypass in Better Auth before 1.6.11 stems from insecure cryptographic defaults in the legacy oidcProvider and mcp plugins, which advertise the 'none' signing algorithm in OIDC discovery and accept plain PKCE by default. Relying parties whose JWT libraries negotiate the algorithm from discovery metadata without pinning can be tricked into accepting unsigned ID tokens, while exposed authorization URLs allow interception of codes because plain PKCE offers no protection. Reported by VulnCheck with a vendor patch available; there is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Cluster attribution spoofing in Wazuh 5.0.0-beta1 and beta2 allows an authenticated enrolled agent to forge wazuh.cluster.name and cluster_node values in inventory-sync FlatBuffer Start messages, because the server validates only the agentid against the enrolled identity while accepting arbitrary cluster metadata fields from the caller. In shared-indexer multi-cluster deployments where numeric agent IDs collide across clusters, a malicious agent can inject inventory and vulnerability documents into a foreign cluster's namespace, corrupting that cluster's security posture data. No public exploit has been identified at time of analysis; exploitation is constrained to pre-release beta deployments and requires an already-enrolled agent, substantially limiting real-world exposure.
Cluster token exposure in ArcadeDB before 26.7.2 enables any authenticated user to escalate privileges to root-level administrative control. The GET /api/v1/server management endpoint returns the arcadedb.ha.clusterToken value in cleartext, which an attacker can replay via the X-ArcadeDB-Cluster-Token and X-ArcadeDB-Forwarded-User HTTP headers to impersonate the root account. This two-stage privilege escalation grants full administrative capabilities including user creation, arbitrary database operations, and server shutdown - representing a near-total system compromise for any multi-tenant or shared ArcadeDB deployment. No public exploit has been identified at time of analysis and this CVE is not listed in the CISA KEV catalog, but the exploitation path is mechanically trivial once credentials are obtained.