Unauthenticated remote clients can force Apache Traffic Server's origin_server_auth plugin to sign attacker-chosen AWS request headers with the proxy's own AWS credentials, potentially allowing access to or modification of origin resources permitted to that identity. The issue affects ATS 8.0.0 through 8.1.11, 9.0.0 through 9.2.15, 10.0.0 through 10.1.4, and 10.2.0, but only installations using the non-default plugin to sign origin requests with AWS credentials are exposed. The vendor rates it High with a CVSS 4.0 base score of 7.0; no public exploit identified at time of analysis.
HTTP request smuggling in Apache Traffic Server 8.0.0 through 8.1.11, 9.0.0 through 9.2.15, 10.0.0 through 10.1.4, and 10.2.0 allows attackers behind a front-end proxy that pools and reuses upstream connections to desynchronize responses and smuggle requests past that front end. The trigger is a client POST carrying 'Expect: 100-continue' when the origin responds before the request body is read, causing ATS to parse the unread body as the next request on the shared connection. Standalone ATS deployments, or those not fronted by a connection-reusing proxy, are not exploitable; no public exploit code or active exploitation was identified at time of analysis.
Improper link resolution in Cisco Expressway Series (TelePresence VCS Expressway lineage) lets a local attacker holding a valid low-privileged account trick a component running at higher privilege into following an attacker-controlled link, producing file read or overwrite with high confidentiality, integrity, and availability impact (CVSS 3.1 base 7.0). Real-world risk is strongly tempered by the exploitability metrics: the attacker must already be present on the appliance (AV:L), must authenticate with low privileges (PR:L), and must satisfy a non-trivial high-complexity precondition such as a race or specific filesystem state (AC:H), with no user interaction (UI:N) and no remote or unauthenticated path indicated. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV.
Predictable root credential generation in D-Link DCS-6501LH firmware 3.03.02, via mydlink_set_root_pwd in /mnt/mtd/aoni_ipc, can give remote attackers root/Telnet access if they can reach the exposed service and derive the weak credential; the attack is high-complexity and the real-world priority is assessed as LOW. CWE-1391 covers the use of weak credentials, and the independent assessment rates confidentiality, integrity, and availability impact as high once the credential is obtained, while the CNA CVSS 4.0 score is 2.9. Publicly available exploit code exists, but no CISA KEV active exploitation is reported in the supplied data.
Missing scheduler-lock protection in Zephyr RTOS's z_waitq_head() helper lets a local unprivileged user-mode thread race the kernel timer expiration handler against thread abort on multi-core builds, yielding use-after-free and out-of-bounds writes performed in supervisor context along with scheduler state corruption; the more common outcome of a lost race is a kernel crash rather than controlled corruption. Only builds with CONFIG_MP_MAX_NUM_CPUS greater than one and CONFIG_USERSPACE enabled are exposed, since the affected code path is a no-op on uniprocessor targets and the required k_timer_start(), k_timer_status_sync(), k_thread_create() and k_thread_abort() primitives are syscalls. Rated CVSS 7.0 (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H); no public exploit code or confirmed active exploitation was identified at time of analysis, and the narrow timing window keeps practical risk conditional rather than drive-by.
Unauthenticated username enumeration in Trudesk through 1.2.11 allows remote attackers to submit crafted regular-expression patterns to POST /api/v1/login and infer valid accounts from distinguishable 'Invalid User' versus 'Invalid Password' responses. The issue is a regex/NoSQL injection in the login lookup (CWE-943) with low confidentiality impact; no public exploit identified at time of analysis and no CISA KEV confirmation. The CVSS 4.0 score is 6.9, and the independent assessment rates it CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N.
Heap out-of-bounds read in FreeRDP clients on Windows before 3.32.1 allows a malicious or compromised RD Gateway to leak client heap memory or crash the client through crafted pre-authentication consent or service messages. The defect is in client_cli_present_gateway_message, where a byte count is misused as a wide-character printf precision, causing roughly twice the intended buffer to be read. No public exploit code has been identified at time of analysis, and exploitation requires the client to connect through an attacker-controlled gateway, for example via lure or network redirection.
Server-side request forgery in SvelteKit before 3.0.0 allows unauthenticated remote attackers to abuse the framework's server-side self-fetch fallback as a redirect-following proxy, reaching internal services by influencing Host or forwarded headers. Exploitation requires that the application uses self-fetch fallbacks and that the attacker can control Host or X-Forwarded-Host/-Proto values, which is realistic behind a misconfigured or trusting reverse proxy; the resulting impact depends on which internal services are network-reachable. No public exploit identified at time of analysis, and the vendor-released fix is SvelteKit 3.0.0.
Unauthenticated data injection in Trigger.dev before 4.5.5 allows remote attackers to write arbitrary content into a run's realtime stream by POSTing to /realtime/v1/streams/:runId/:streamId. The handler has no auth wrapper and the run lookup is not scoped to a runtime environment, so a known or guessed predictable friendlyId (e.g. run_1234abcd) can reach production streams, though impact is bounded to integrity of stream data with no read access, code execution, or availability loss. No public exploit code identified at time of analysis.
Memory exhaustion in adm-zip 0.6.0 and earlier allows unauthenticated remote attackers to bypass the library's decompression-bomb guard on the asynchronous getDataAsync() path, causing the full decompressed payload to be allocated regardless of an entry's declared uncompressed size. This is a genuine but bounded availability issue: only Node.js applications that read ZIP entries asynchronously and rely on the declared size as their bomb protection are exposed, there is no confidentiality or integrity impact, and meaningful denial of service typically requires repeated or large crafted submissions. Publicly available exploit code exists in the form of a working proof-of-concept published with the GitHub advisory, and the flaw is fixed in adm-zip 0.6.1.
Apache Traffic Server can be stalled by a crafted chunked HTTP transfer whose trailers ATS has been configured to strip: the proxy discards the trailer bytes but still waits for them, so the transaction hangs until the connection timeout expires. Versions 10.0.0 through 10.1.4 and 10.2.0 are exposed in their default configuration because proxy.config.http.drop_chunked_trailers is enabled by default in the 10.x line, while 8.1.11 and 9.2.5 through 9.2.15 are affected only where an operator has explicitly turned that setting on. Rated CVSS 5.3 (AV:N/AC:L/PR:N/UI:N, availability-only Low), this is a modest denial-of-service issue that degrades individual proxied connections rather than the whole service; no public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited.
Unauthenticated network access to the shared proxy cache is possible in Apache Traffic Server deployments that load and enable the experimental tsmemcache plugin, allowing remote attackers to read, modify, and delete cached objects without credentials. Affected releases span 8.0.0 through 8.1.11, 9.0.0 through 9.2.15, 10.0.0 through 10.1.4, and 10.2.0; the exposure is gated by the plugin being explicitly enabled and its memcache-style interface being network-reachable, since it is not active in a default installation. No public exploit code or confirmed active exploitation was identified at time of analysis, though the CVSS 4.0 base score of 9.4 and the unauthenticated nature of the interface once exposed make this a high-priority fix for anyone running the plugin.
Information disclosure in pdfmake 0.3.8 through 0.3.11 lets attackers read local files that the setLocalAccessPolicy() restriction is supposed to block, by placing an SVG image whose href points at a local path. The flaw is reachable by unauthenticated remote attackers (CVSS v4 PR:N) but only matters when a host application builds PDFs from attacker-influenced document definitions and relies on that policy to sandbox file access; impact is limited to confidentiality. No public exploit code or confirmed active exploitation was identified at time of analysis, and a vendor patch ships in 0.3.12.
Heap out-of-bounds read in the FreeRDP Android client before 3.32.1 allows a malicious or compromised RDP server to read past allocated surface buffers by supplying unvalidated mappedWidth and mappedHeight values in an RDPGFX_MAP_SURFACE_TO_WINDOW_PDU. Only Android client builds of FreeRDP that negotiate the graphics pipeline (RDPGFX) channel are affected, and because the attack direction is server-to-client, a victim must first be induced to connect to the hostile endpoint - there is no way for an attacker to reach arbitrary hosts directly. Successful exploitation yields limited heap memory disclosure and possible client crashes, with no code execution or write primitive described; no public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis, and the CVSS:4.0 score of 6.9 is driven by low confidentiality impact combined with network reachability.
Missing authorization checks in the legacy AJAX handlers of Chamilo LMS 2.0.0 pre-releases (2.0.0-alpha.1 through RC.2) let unauthenticated remote attackers enumerate learner accounts and pull other users' certificate PDFs by calling actions such as get_users_by_group_course, user_by_all_roles and export_all_certificates. Impact is confined to confidentiality (user names and certificate documents); there is no write, modification or availability effect, and stable 1.x production installations are not in the affected range. The independent assessment rates this as a genuine but moderate-severity information-disclosure issue (CVSS v4.0 score of 6.9, assessed CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/C:L), and no public exploit code or CISA KEV entry was identified at time of analysis.
Request body inspection bypass in Coraza WAF versions 3.0.4 through 3.8.0 allows unauthenticated remote attackers to evade custom body rules by sending a valid URL-encoded form body with a Content-Type parameter such as 'application/x-www-form-urlencoded; charset=UTF-8', leaving ARGS_POST and REQUEST_BODY empty while the backend still parses the payload. This is a moderate-priority WAF evasion issue rather than a server compromise; deployments that rely on custom ARGS_POST or REQUEST_BODY rules are exposed, while an unmodified current OWASP CRS with rule 901340 forces fallback inspection and neutralizes the bypass. No public exploit identified at time of analysis; vendor-released patch: 3.8.1.
Any authenticated Trudesk user can read tickets belonging to groups they are not a member of - subject, issue body, comments, ticket owner and assignee - by simply iterating sequential ticket IDs against GET /api/v1/tickets/:uid, and every release through 1.2.11 is affected. The apiTickets.single handler omits the group-membership check entirely, making this a textbook IDOR (CWE-639) instead of an injection or memory-safety bug, so attacker impact is limited to read-only disclosure with no modification or code execution. Risk is medium (CVSS 5.3; our assessment CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N): the only prerequisite is a valid account at any privilege level, no public exploit code or confirmed active exploitation has been identified at time of analysis, and instances that permit self-registration or host many low-privilege accounts should be treated as the highest exposure.
HTTP request smuggling in Apache Traffic Server (8.0.0 through 8.1.11, 9.0.0 through 9.2.15, 10.0.0 through 10.1.4, and 10.2.0) lets unauthenticated remote attackers send HEAD requests carrying Content-Length or Transfer-Encoding headers to desynchronize HTTP message framing between ATS and an upstream or downstream agent. The scope-changed CVSS 3.1 score of 9.3 (AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:N) reflects high integrity impact - cache poisoning, request/response queue confusion, and possible access-control bypass - with limited confidentiality exposure; no public exploit code was identified at time of analysis. Vendor-released fixes are available in 9.2.16, 10.1.5, and 10.2.1.
JSON body inspection bypass in Coraza 3.0.0 through 3.8.1 lets unauthenticated remote attackers hide SQL-injection payloads from OWASP CRS rules while the backend still receives and processes them. The flaw is in Coraza's JSON body processor, which flattens nested objects into dot-separated ARGS_POST names without escaping dots that appear literally in property names, so a decoy sibling key such as "account.role" overwrites the flattened entry for the nested "account.role" value inside Coraza's map while standard backend JSON parsers keep both properties intact. Real-world impact is conditional: the bypass only matters where the protected application has an injectable downstream sink, though the vendor advisory demonstrates the evasion working against CRS v4.25 rule 949110; no public exploit code was identified and there is no KEV/active-exploitation signal, and independent assessment rates the direct risk as integrity-only (CVSS 3.1 5.3, C:N/I:L/A:N) rather than as code execution.
Unauthenticated gradebook certificate tampering affects Chamilo LMS 2.0.0 pre-release builds (alpha.1 through RC.2), where the GradebookController set_default_certificate endpoint lacks authorization checks and lets any remote user supply an arbitrary course id and document id to alter certificate configuration. The independent assessment rates this moderate severity (CVSS 3.1: 6.9, AV:N/AC:L/PR:N/UI:N with integrity-only, low impact), and exploitation is constrained to unpatched pre-release deployments that are network-reachable. No public exploit code or confirmed active exploitation is identified in the available data, and the vendor has released a fix in 2.0.0-RC.3.
adm-zip versions before 0.6.1 can apply attacker-controlled setuid, setgid, or sticky bits when extracting archives with the non-default keepOriginalPermission option enabled. This is a conditional local privilege-escalation risk: the archive must be extracted in a privileged context such as root and the resulting executable must later be run, so exploitation depends on that specific workflow. No public exploit identified at time of analysis, and the vendor-released patch is adm-zip 0.6.1.
Information disclosure in TP-Link Deco BE63 v2.0 lets an attacker who already holds administrative privileges on the device, and can reach it from an adjacent LAN or Wi-Fi segment, query the cloud-client daemon and recover the linked TP-Link ID account password in plaintext. That credential could then be used to access the associated TP-Link cloud account and perform actions as the affected user. The vendor has released a firmware update, and no public exploit was identified at time of analysis; the independent assessment rates this as a constrained medium-severity risk because exploitation requires admin access and adjacent-network positioning.
Trigger.dev CLI versions before 4.5.9 can disclose resolved environment secret values when deployment is run with debug logging, because the debug output serializes the build-worker options object with unredacted envVars; this exposes database connection strings and service credentials to anyone who can read the resulting terminal transcript, CI debug log, captured tool output, or support bundle. The assessed impact is confidentiality-only (CWE-532, CVSS:3.1 AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N), and exploitation is constrained by the need for debug-level logging and access to retained output; normal non-debug environment listings redact values. Trigger.dev 4.5.9 contains the vendor fix, and no public exploit code is identified at time of analysis.
GitLab Enterprise Edition lets a group Owner re-enable AI-backed GitLab Duo data egress for their group and all descendant projects even after an instance administrator has explicitly locked Duo availability for that group, defeating the administrator's control (CWE-863). Only EE instances on 19.2 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 are affected, and only where an admin lock was actually configured; Community Edition and instances without a Duo lock are unaffected. Requirements are strict - an authenticated group Owner on the target group (CVSS PR:H, 2.7 score) - so this is a trusted-insider bypass with limited integrity impact, not a mass-exploitable flaw; publicly available exploit code exists via a HackerOne report, and no active exploitation has been confirmed (not in CISA KEV).
Customer record disclosure in the WordPress Appointment Booking Plugin before 5.7.5 allows any authenticated agent-level user to read and enumerate personal information for customers managed by other agents, because the plugin's customer retrieval and search functions omit the agent-to-customer assignment check (CWE-639). The issue is remotely reachable but requires an existing agent credential (no anonymous access), has confidentiality-only impact, and is low severity at CVSS 2.7 (independently assessed as PR:L rather than the supplied PR:H). Publicly available exploit code exists, and vendor fixes are available in 5.7.5, but there is no CISA KEV confirmation of active exploitation.
Authenticated WordPress users with at least the Contributor role can set attacker-chosen prices for existing products in Simple Shopping Cart before 5.3.3, and any visitor can then add those items to the cart at the manipulated price. The plugin does not validate submitted product prices against an owner-only reference value, so the impact is limited to price integrity rather than data disclosure or service disruption. Publicly available exploit code exists, but there is no KEV entry confirming active exploitation, and the issue is low priority because the attacker must already hold Contributor access.
Insecure temporary file handling in Cisco Expressway Series allows a local, low-privileged attacker to tamper with data and disrupt services when another user or process interacts with an attacker-influenced temporary file (CVSS 6.6; AV:L/PR:L/UI:R, C:N/I:H/A:H). The flaw is tracked as CWE-377 and affects the Cisco Telepresence Video Communication Server (VCS) Expressway product line; the available CPE data does not identify a specific version range. No public exploit code or confirmed active exploitation was identified in the provided intelligence at time of analysis.
Crafted relationship-inclusion parameters on Laravel JSON:API resource endpoints can be turned into destructive database operations, letting a low-privileged user wipe data from related tables through what should be a read-only request. Applications running laravel/framework versions 12.45.0 through 12.67.x, or 13.x before 13.27.0, that expose client-controlled 'include' query parameters via the JsonApiResource / ResolvesJsonApiElements feature are affected; the vendor fixed the flaw in 12.68.0 and 13.27.0. Because a single request can irreversibly empty tables, the integrity and availability impact outweighs the modest attack complexity, though exploitation is conditional on JSON:API resources actually being adopted and on the endpoint honoring user-supplied includes - no public exploit code or confirmed active exploitation was identified at time of analysis.
Denial of service in Splunk Enterprise allows a low-privileged authenticated user to render the entire instance unavailable, requiring a manual restart to restore service. The flaw is a missing resource-consumption limit in the REST API endpoint for lookup table files, which fails to bound response field selections (CWE-770). Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16 are affected; exploitation requires only a valid Splunk account (PR:L) that need not hold the admin or power roles, and no public exploit code or active exploitation has been identified at time of analysis. Impact is strictly availability - no data confidentiality or integrity loss - making this a genuine but moderate-priority issue that escalates in environments with broad API access.
Broken access control in Nuxt (3.11.0 through 3.21.4 and 4.4.4) lets unauthenticated remote attackers retrieve pages that routeRules and appMiddleware are meant to gate, by requesting a percent-encoded form of a protected path that contains a dynamic or catch-all parameter. Route-rule keys are compared against the raw request path, while Vue Router decodes the parameter during route resolution, so the gating rule never matches and the page plus its SSR data payload is returned to the requester; the same mismatch also breaks redirect, appLayout, ssr, prerender and cache/isr/swr-derived payload rules in the app manifest. CVSS 3.1 is 6.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N) - moderate, limited confidentiality and integrity impact - and no public exploit code or confirmed active exploitation was identified at time of analysis; exposure is limited to applications that actually gate dynamic/catch-all routes via route-level rules.
Denial-of-service in Pillow's multi-frame image handling: the MAX_IMAGE_PIXELS decompression-bomb guard can be bypassed for MPO, DCX, and MIC containers when an application calls seek() to navigate to frames or pages beyond the first, allowing a small attacker-supplied file to trigger unbounded memory and CPU consumption. Only applications that open these specific multi-frame formats and seek past the first frame are affected; single-frame opens and first-frame-only pipelines are not. The flaw is rated CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L (availability-only, no confidentiality or integrity impact), affects Pillow releases prior to 13.0.0, and no public exploit code was identified at time of analysis.
Integer underflow in Pillow's legacy PILfont text-width calculation (CVE-2026-96641, GHSA-4rm8-3hmm-39fg) can be triggered when an application loads and measures text with a manipulated .pil bitmap font, producing a low-impact availability condition; the Pillow project rates it Medium and fixed it in release 13.0.0. The assessed CVSS 3.1 vector is AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L, indicating a local attack vector, no privileges required, no user interaction, and impact limited to availability with no confidentiality or integrity effect. No public exploit was identified at time of analysis, and no CISA KEV entry is indicated in the available data.
Splunk SOAR deployments below 8.7.0 allow any authenticated user whose role omits the view-apps permission to export and download an installed app archive, exposing proprietary source code and any sensitive data or secrets embedded in that package. The flaw is a missing authorization check in the app export path, rated CVSS 6.5 with confidentiality-only impact. No public exploit code or CISA KEV entry was identified at time of analysis, and exploitation requires a valid low-privileged account on the SOAR instance.
Splunk Secure Gateway exposes mobile alert notification data belonging to other users to any authenticated low-privileged account that lacks the admin Splunk role or sc_admin Secure Gateway role. The flaw is missing user-level authorization on read requests to certain Secure Gateway App Key Value Store (KV Store) REST API collections, and it affects Splunk Enterprise releases below 10.4.4, 10.2.8, 10.0.11, and 9.4.16 plus Secure Gateway releases below 3.10.12, 3.9.26, and 3.8.73. No public exploit has been identified at time of analysis, and the vendor-assigned CVSS 3.1 score is 6.5 with a confidentiality-only impact.
Reflected and stored cross-site scripting can occur in Astro Framework versions prior to 7.3.2 when an application passes attacker-controlled data as a dynamic child of a <script> or <style> element rendered through the astro:jsx renderer, including MDX components. Exploitation is conditional on that developer-introduced pattern-compiler-generated literal script/style content and other JSX expression contexts are not affected-and requires the victim to load the crafted page (UI:R). No public exploit code was identified at time of analysis; the NVD score is 6.5, while our independent assessment treats impact as limited (S:C/C:L/I:L/A:N) because the vulnerable pattern is not a default configuration.
An authenticated user who is permitted to submit evaluation jobs in Red Hat OpenShift AI's lm-evaluation-harness component can supply an attacker-controlled model URL in the JobSpec, causing the evaluation job pod to send the tenant's model authentication secret to an external listener the attacker controls. The same user-controlled URL handling allows Server-Side Request Forgery against internal endpoints reachable from the evaluation pod's network namespace, so internal services can be probed or reached with the pod's network position rather than the attacker's. The impact is confidentiality-only (CVSS 3.1 base 6.5, PR:L, C:H/I:N/A:N), no public exploit code or confirmed active exploitation was identified at time of analysis, and exploitation is gated on valid tenant job-submission credentials plus network reachability from the pod.
Cross-tenant role manipulation in hMailServer 6.3.4 through 6.3.6 allows an authenticated credential confined to named domains - either a full-scope REST API key issued for those domains or a serveradmin account assigned a domain list - to create, rewrite, or delete custom roles globally through the REST role-management routes. Because those routes require manage_roles and name no domain, the authorization gate does not scope the operation to the caller's tenant, so an attacker can raise or lower the permissions of a custom role assigned to another domain's accounts; the reachable damage is bounded because custom roles cannot carry administer_server, administer_domain, or manage_roles. No public exploit identified at time of analysis, and exploitation is meaningful only in multi-tenant deployments where custom roles are assigned across domains.
NLnet Labs Unbound up to and including 1.26.1 can be tricked into downgrading a validly signed island-of-security zone to insecure status by a forged NXDOMAIN response, allowing an attacker to deny the existence of records inside that trusted island. The flaw only manifests in the non-default configuration where a root trust anchor and an explicit 'trust-anchor:' statement for an island-of-security zone are both present and the island's parent is provably insecure under the root chain; the attacker must also be positioned to deliver a crafted NXDOMAIN carrying an NSEC/SOA RRSIG whose SignerName names the insecure parent. No public exploit code or confirmed active exploitation was identified at time of analysis, and the high attack complexity and specialized configuration keep practical risk moderate (CVSS 6.5, AV:N/AC:H/PR:N/UI:N/C:N/I:L/A:H).
Splunk SOAR (On-premises) deployments below 8.7.0 allow an authenticated user with REST API access to alter the Enterprise Security edition and trigger an unauthorized license change, because the application authenticates the request but fails to authorize the caller before applying the change. The flaw is an integrity-only issue (CVSS 6.5, PR:L) and does not expose data or disrupt availability; no public exploit code or confirmed active exploitation was identified at time of analysis.
Apache bRPC through 1.17.0 can be remotely aborted by an unauthenticated attacker who sends a crafted HTTP/2 HEADERS block that exhausts the HPACK dynamic-table ring buffer while staying under the byte-based eviction threshold. The h2 parser is enabled by default on bRPC server ports and processes headers before Authenticator checks, so any exposed h2/gRPC listener is sufficient; the assessed impact is availability-only (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). No public exploit identified at time of analysis, and no KEV listing or EPSS score was present in the supplied data.
Cross-site request forgery in the Tailored Tools WordPress plugin (versions up to and including 3.0.3) lets an attacker who can lure a logged-in privileged WordPress user - typically an administrator - to a malicious page or link silently perform state-changing actions that the victim's session is authorized to make. The attacker needs no account of their own (CVSS 6.5, AV:N/PR:N/UI:R), but the attack only succeeds if the victim is authenticated at the moment of interaction, so confidentiality is unaffected while integrity impact is rated High. Reported by Patchstack; no public exploit code or confirmed active exploitation was identified at time of analysis.
Missing authorization (CWE-862) in the BjornTech Swish for WooCommerce WordPress plugin at versions up to and including 3.7.8 lets unauthenticated remote attackers reach plugin endpoints that perform no access-control check, yielding limited reads and modifications of the protected Swish payment functionality (CVSS 6.5, AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N). Only WooCommerce stores running this Sweden-specific Swish mobile-payment integration are exposed, so the practical attack surface is narrow geographic/vertical footprint rather than mass exploitation. No public exploit code has been identified at time of analysis, no CISA KEV listing applies, and no EPSS score was supplied with the source data.
Stored cross-site scripting in the Contest Gallery WordPress plugin through version 34.0.1 allows an authenticated low-privilege user to persist malicious markup that later executes in another user's browser when the tainted page is rendered. Because the injected script runs in the victim's context (scope changed, C:L/I:L), an attacker could perform limited actions as the viewer, such as altering displayed content or bypassing page-level protections. No public exploit code was identified at time of analysis, and the issue has not been confirmed actively exploited (CISA KEV).
Heap-based memory corruption in NTPsec ntpd before 1.2.6 affects deployments that explicitly enable the non-default JJY refclock driver in Telephone JJY mode (refclock type 40). An unauthenticated attacker with physical/local control of the Telephone JJY time source can send more than six time replies to the driver, causing heap corruption, an ntpd crash, and high integrity/availability impact; the CVSS score is 6.4 but real-world priority is low because stock configurations do not enable this region-specific driver. No public exploit code was identified at time of analysis.
Pillow 11.2.1 through 12.x can disclose uninitialized padding, bytes preceding the first row, or stale heap contents when an application sets a non-default PILLOW_ALIGNMENT and exports images through the Arrow C interface (__arrow_c_array__/__arrow_c_schema__). The flaw is limited to deployments that both customize alignment and use Arrow export, with meaningful cross-user exposure requiring a multi-user context where one user's exported buffer can reach another user; default Pillow configurations are not affected. No public exploit code or CISA KEV entry was identified at time of analysis, and the vendor released Pillow 13.0.0 as the fix.
Pydantic AI Harness versions before 0.59.0 fail to enforce the operator-configured UsageLimits.tool_calls_limit for nested tool invocations dispatched from inside a sandboxed run_code snippet in the CodeMode toolset, letting a program call run_nested_call() repeatedly and reach costly or side-effecting tools far beyond the intended ceiling. Unauthenticated remote attackers who can shape the agent's execution - as a user of the agent or through prompt-injected content - can therefore bypass a guardrail that operators rely on for cost and safety control, with impact bounded to resource exhaustion/limit violation rather than data exposure or code execution. This is a moderate CWE-770 resource-throttling flaw; no public exploit code or active exploitation was identified at time of analysis, and the vendor has released 0.59.0 to correct it.
Improper authorization in the HarnessRouter gateway through version 0.31.10 lets a request that carries the internal key plus a non-verifying bearer token assert arbitrary X-Harness-Org and X-Harness-Member identity headers, because the gateway's default identity mode was 'observe' rather than a fail-closed 'enforce'. This enables cross-tenant impersonation of any organization or member, with Low confidentiality, integrity, and availability impact; the attack is remote but rated high complexity and difficult to exploit, and no public exploit code or active exploitation has been identified at time of analysis. HarnessRouter 0.31.11 changes the default to 'enforce' and closes the issue.
Route-rule matching in Nuxt versions prior to 4.6.2 can be evaded by changing only the letter case of a request path, because Nuxt's page resolver is case-insensitive by default while Nitro's server-side route-rule keys are matched case-sensitively. A remote, unauthenticated attacker who requests a case-variant of a protected route can cause redirects, custom headers, proxy rules, ssr: false and noScripts to be skipped, and can make getRouteRules(event)/matchRouteRules return no rule at all for that path. This is a configuration-dependent security-control bypass rather than a high-urgency flaw: applications that set router.options.sensitive: true in nuxt.config are unaffected, and access checks implemented in server middleware, page route middleware or page data fetching remain independent and are not bypassed. No public exploit code or confirmed active exploitation was identified at time of analysis; the issue is addressed by the vendor fix in 4.6.2.
Concurrent constrained-decoding traffic against vLLM servers running versions before 0.31.0 can leave a stale token allowlist in a recycled batch slot, so a victim's unrestricted generation request is silently constrained to the attacker's token set. The flaw is in InputBatch.condense(), which recycles finished request slots without clearing allowed_token_ids; remote unauthenticated attackers who can reach the generation API, including the unauthenticated /invocations endpoint, can trigger it by submitting many concurrent constrained requests while a race with slot reuse is won. Impact is integrity-only - the victim's output is degraded or steered, but no victim data is read - and success is timing- and load-dependent (CVSS AC:H with attack requirement AT:P). No public exploit code or confirmed active exploitation has been identified at time of analysis, and the issue is fixed in vLLM 0.31.0.
Contracts written in Vyper 0.3.8 through 0.5.0b1 that use a ternary expression to select between nested arrays with differing inner bounds can silently store corrupted values or revert at runtime, because the compiler emits code that reads the narrower arm using the wider result type's memory layout. Only deployments that already contain this specific widening nested-array ternary pattern are exposed, and no public exploit code has been identified at time of analysis. The impact is confined to the integrity of the affected contract's own state (CVSS 4.0 6.3 Medium, VI:L with no confidentiality or availability impact), so contracts lacking the pattern are entirely unaffected.