Cross-site request forgery in the LuCI administrative web interface of Advantech EKI-1242IEIMS running firmware V1.06.01 allows a remote, unauthenticated attacker to make an authenticated administrator's browser issue unauthorized state-changing requests, reaching privileged device management functions with high integrity and availability impact (vendor CVSS 4.0 base 8.6; independent 3.1 assessment AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H). Exploitation is conditional and social-engineering dependent: the administrator must hold an active LuCI session and be lured into visiting attacker-controlled content, so the technique fails against logged-out or idle-session administrators and reliability is constrained by the required user interaction. No public exploit code or confirmed active exploitation was identified at time of analysis.
Out-of-bounds memory writes in LightGBM through 4.7.0 can be triggered when a text-format model file containing invalid child/split node references is loaded and SHAP feature-contribution prediction (pred_contrib) is subsequently run, letting the attacker control where data is written inside the leaf_depth_ buffer. The flaw is classified CWE-787 (out-of-bounds write) with a high impact on confidentiality, integrity and availability (CVSS 4.0 base 8.5; independently assessed as CVSS 3.1 AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), and exploitation is not remote: per the CVSS vector the attack is local (AV:L) and requires user interaction, meaning the victim must open a malicious model and execute the SHAP prediction path. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and environments that only load trusted, self-generated models or that never compute feature contributions are not exposed.
Privilege escalation in the remote diagnostics debugger of Cisco Secure Firewall Management Center (FMC) lets an authenticated, remote user turn a valid low-privileged account into root. The flaw is a faulty privilege-level check (CWE-264) applied when a user invokes remote diagnostics, so an attacker who can log into either the web-based management interface or the REST API can enable the debugger service and have it grant them elevated rights; Cisco rates the exploitation path High complexity because it requires a multi-stage sequence rather than a single crafted request (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H, 8.5). Because the attacker must already hold valid credentials on the device (PR:L), this is an access-gated escalation and not an unauthenticated entry point; no public exploit code has been identified and the issue is not confirmed as actively exploited (not in CISA KEV), though the scope-change impact (S:C) means a compromise of the debugger context can affect resources beyond the vulnerable component. Affected releases reported through EUVD are FMC 7.7.0, 7.7.10, 7.7.10.1, 7.7.11, 7.7.12, 10.0.0 and 10.0.1.
Incorrect default permissions in Dell Repository Manager (DRM) versions prior to 3.5.2 let an attacker who already holds a low-privileged account on a Windows host abuse misconfigured files, directories, or service resources to escalate to a higher-privileged context. Dell rates this 8.5 (High) with a remote, scope-changing vector (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H), but our independent assessment scores it 7.8 as a local privilege-escalation issue (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H): exploitation requires an existing foothold on a machine where DRM is installed, is not a default unauthenticated remote scenario, and is limited to systems running DRM below 3.5.2. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the vendor has published a fixed release (3.5.2) via Dell security advisory DSA-2026-419.
Heap-based memory corruption in NLnet Labs Unbound up to and including 1.26.0 lets a remote, unauthenticated attacker who controls or spoofs the upstream DNS response (PR:N/UI:N) gradually overwrite heap memory, with the reliable outcome being a crash and remote code execution possible only on certain systems and compilation options that lack hardening. The flaw is scored CVSS 8.4 (CVSS:4.0) and by the independent assessment as CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, with the high attack complexity reflecting heavy dependence on heap layout and non-deterministic results. No public exploit code and no confirmed active exploitation were identified at time of analysis, and no KEV listing or EPSS signal is present, so this is a genuine but not-yet-urgent priority for internet-facing recursive resolvers.
Mounting a crafted NTFS filesystem image can corrupt Linux kernel memory through the in-kernel fs/ntfs3 driver, where an integer truncation in restart-table growth (a u32 'used + add' cast to the u16 __le16 count of struct RESTART_TABLE) produces an undersized allocation that is subsequently written past its bounds during $LogFile replay. The issue is local and requires an attacker-supplied image to actually be mounted: on default configurations this needs mount privileges (CAP_SYS_ADMIN/root), while the unprivileged path depends on a USB-automount daemon plus physical insertion of the media, so it is not remotely reachable. Kernels carrying the vulnerable ntfs3 log-replay code before the listed stable fixes are affected; vendor patches are available (Linux 5.15.221, 6.1.188, 6.6.157, 6.12.110, 6.18.52 and 7.2.6, plus 7.3-rc1 in mainline), no public exploit was identified at time of analysis, and EPSS is low at 0.21% (11th percentile).
Mounting a crafted NTFS image on a Linux system with the ntfs3 driver loaded triggers an out-of-bounds read in read_log_rec_buf(), causing a kernel crash and possible disclosure of adjacent slab memory into the log replay buffer. This is a local-only issue that requires the attacker to get the malicious volume mounted, either through physical media with an active automount daemon or a process/user holding mount privileges such as CAP_SYS_ADMIN, and no public exploit was identified at the time of analysis. Vendor patches are available in stable releases 5.15.221, 6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6, and 7.3-rc1, and the independent assessment (AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H) is lower than the provided 8.4 vector because impact is limited to crash and potential disclosure rather than code execution.
Multiple internally-discovered coding-standard defects in Cisco Secure Firewall ASA Software, Threat Defense (FTD) Software, and Firewall Management Center (FMC) Software can be triggered by an attacker who already holds high-privilege administrative credentials and who can also induce a separate user interaction, potentially yielding high confidentiality, integrity, and availability impact that crosses a security scope boundary (CVSS 8.4, CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H). The affected trains span ASA 9.16 through 9.24, FTD 7.0 through 10.0.0, and FMC 7.0 through 10.0.1. Cisco addressed these issues as a grouped hardening release (CWE-710, Improper Adherence to Coding Standards) rather than a single disclosed flaw; no public exploit code was identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV).
Command injection weaknesses in HP Linux Imaging and Printing Software (HPLIP) allow a local attacker to execute arbitrary operating-system commands with the privileges of the affected HPLIP component, resulting in high confidentiality, integrity, and availability impact (vendor CVSS 4.0 base 8.4) and spanning remote code execution, privilege escalation, denial of service, information disclosure, and unauthorized file modification. Exploitation is not remote: it requires local access to a Linux host that has HPLIP installed and in use, and it requires active user interaction, typically by inducing a legitimate user to feed attacker-controlled input into a vulnerable HPLIP component that builds an OS command (CWE-78). No authentication or elevated privileges are needed (PR:N), and no public exploit code or confirmed active exploitation was identified at time of analysis; HP has released remediation for the affected components in advisory HPSBPI04151.
Sandbox escape in RestrictedPython versions prior to 8.4 lets code executing inside the restricted context reach host-level primitives - function globals, builtins, file access, and code-execution gadgets - whenever the host exposes the standard-library string module, the string.Formatter class, a Formatter instance, or a Formatter subclass to that restricted code. The prerequisite is non-default: stock RestrictedPython does not surface these objects, so a custom import policy or specially crafted globals must be in place, and the attacker must also be able to submit restricted Python code (typically an authenticated user of the hosting application). A vendor patch is available in 8.4; no public exploit was identified at time of analysis.
Cross-site request forgery in the WNC T-Mobile 5G Box IDU router (portal.cgi) lets a remote attacker drive privileged actions through an already-authenticated administrator's browser, because the anti-CSRF check accepts any value supplied in the csrf_token_value parameter. The flaw affects firmware versions below 1.1.0.651412, is rated 8.4 under CVSS 4.0 (AV:A/PR:N/UI:A, high confidentiality and integrity impact, low availability impact), and requires the victim to be logged into the router portal while being lured to an attacker-controlled page reachable over the adjacent network. There is no confirmed active exploitation (not listed in CISA KEV) and no public exploit code identified at time of analysis; the vendor has released a fixed firmware build, so risk is real but conditional rather than an emergency patch-now scenario.
Improper freeing of a kernel heap buffer in the Linux kernel's cpuidle device-tree idle power-domain support (dt_idle_genpd) can crash affected systems when a device-tree idle power domain is torn down. Kernels built with CONFIG_DT_IDLE_GENPD and instantiated DT idle power domains - introduced by commit 9d976d6721df (present since Linux 5.18) and fixed in stable releases 6.1.188, 6.6.157, 6.12.110, 6.18.51 and 7.2.5/7.3-rc2 - are affected, which in practice means ARM/embedded PSCI-style platforms whose firmware provides cpuidle power-domain nodes. Triggering requires local privileged or boot-time influence over device-tree content or the ability to force genpd teardown/probe failure, so this is not remotely reachable and no public exploit has been identified at time of analysis; the practical impact is a kernel crash rather than code execution or data disclosure, despite the 8.4 base score reported by NVD-style scoring (our own assessment is AV:L/AC:H/PR:H with C:N/I:N/A:H).
Uninitialized spinlock use in the Linux kernel's ALSA 'harmony' driver (HP PA-RISC CS4215 sound hardware) can crash the system during driver initialization, because snd_harmony_create() calls request_irq() before h->lock and h->mixer_lock are initialized and a pending interrupt can fire the handler against garbage lock state. Only systems with this legacy driver present and probing on real or emulated PA-RISC hardware are exposed, and triggering it requires a narrow hardware timing window during boot or root-privileged module load, so there is no public exploit identified at time of analysis and independent assessment rates real-world risk as low despite the vendor's 8.4 (HIGH) score - the assessed impact is availability-only (local denial of service/crash) under a privileged, high-complexity precondition. Vendor patches have been published as upstream commits and are shipped in the stable releases listed below.
A missing error check in the Linux kernel's Loongson ASoC sound-card ACPI probe path (loongson_card_parse_acpi) leaves the pointer returned by device_property_read_string() for the 'codec-dai-name' property uninitialized when that property is absent or invalid, and the stale pointer is dereferenced later during driver binding. Only LoongArch/Loongson platforms whose ACPI firmware omits or malforms codec-dai-name are affected, and reaching the bug requires the ability to supply or modify that firmware description - it is not reachable over the network and not triggerable by an unprivileged local user on a default, correctly-described platform. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV; the vendor's CVSS 8.4 rating substantially overstates the assessed risk (CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:H), and the vendor vector is also internally inconsistent because it computes to 7.8 rather than 8.4.
LoongArch Linux kernels overflow the fixed-size acpi_package_ids[] array while parsing the ACPI PPTT table, so a system whose firmware or hypervisor advertises more CPU packages (sockets) than the array can hold crashes during topology setup - the concrete case in the description being a LoongArch virt VM configured with one core per socket for up to 256 sockets. Affected builds are those before the fixed 6.12.110, 6.18.51, 7.2.5 and 7.3-rc1 kernels; the flaw is reachable only on LoongArch, and the assessed precondition (per our independent analysis: AV:L/AC:H/PR:H, C:N/I:L/A:H) is control over the guest's ACPI topology rather than an ordinary unprivileged runtime action, with the practical outcome being a boot-time crash and memory corruption rather than remote code execution. No public exploit code was identified at the time of analysis and there is no CISA KEV record, so this is not confirmed as actively exploited; the vendor has released patches and the relevant upstream commits are public.
Double-decrementing the SCP device reference in the Linux kernel's MediaTek MDP3 (mtk-mdp3) media platform driver can free or unbalance a device object that the driver still uses, producing driver instability and potentially a use-after-free on systems that take the fallback SCP lookup path. The flaw is only reachable when scp_get() fails during mdp_probe() so that __get_pdev_by_id() runs; the reference taken by that fallback is dropped immediately, yet scp_put() is later called unconditionally from the probe error path and from mdp_video_device_release(). Exposure is confined to local presence on embedded MediaTek SoC hardware running the affected driver, the triggering scp_get() failure is a non-default condition rather than an attacker-controlled input path, and no public exploit code has been identified at time of analysis. Although NVD scores this 8.4, our independent assessment rates it CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H - high severity but low realistic risk.
The Linux kernel's saa7164 media driver can leave a freed device structure dangling on the global saa7164_devlist when PCI BAR memory-region allocation fails during probe, because saa7164_dev_setup() adds the device to the list before calling get_resources() and never removes it on that error path; the probe cleanup then frees the device while the global list still points at it. Affected systems are those running the saa7164 driver against an SAA7164-based (NXP/Philips) TV capture card such as a Hauppauge HVR-22xx, and effectively any kernel built with CONFIG_VIDEO_SAA7164; the flaw was introduced with commit 443c1228d50518f3c550e1fef490a2c9d9246ce7 and is fixed in Linux 6.1.188, 6.6.157, 6.12.110, 6.18.51 and 7.2.5 (mainline 7.3-rc1). No public exploit has been identified at time of analysis (no CISA KEV entry, no published POC, no EPSS signal in the supplied data), and the vendor's CVSS 8.4 is not supported by our independent assessment, which rates the issue CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L and concludes real-world risk is LOW: the trigger is a hardware/probe-time resource failure rather than an attacker-controlled input, there is no remote vector, and no default configuration is affected.
Memory corruption and kernel crashes in the Linux kernel's qla2xxx QLogic Fibre Channel HBA driver arise from an integer truncation when the driver derives its request/response queue counts from the adapter's advertised MSI-X vector count. Affected systems are those running the CONFIG_SCSI_QLA_FC driver and bound to a QLogic FC HBA that reports a boundary MSI-X count (257 vectors, which truncates to zero in the u8 queue-count fields, or exactly 1), after which qla2x00_alloc_queues() obtains ZERO_SIZE_PTR from kzalloc_objs(struct req_que *, 0) and then dereferences it via ha->req_q_map[0]; target-mode configurations can additionally underflow max_req_queues from 0 to 255. Exploitation requires physical or firmware-level control of a PCI/FC device (per our independent assessment of CVSS:3.1/AV:P/AC:H/PR:N/UI:N, C:N/I:L/A:H) rather than any network or unprivileged-user input, and there is no public exploit identified at time of analysis. Vendor patches are available in the referenced stable tree commits.
Signed integer overflow in the Linux kernel ofdrm (Open Firmware framebuffer) driver allows the framebuffer size computation fb_size = linebytes * height to wrap when both geometry values are large, resulting in an undersized framebuffer allocation and subsequent out-of-bounds memory handling inside the drm/sysfb subsystem. Exposure is confined to systems that actually bind the ofdrm driver, effectively Open Firmware/PowerPC-class platforms whose linebytes and height come from firmware or the boot device tree rather than from runtime user input, and the assessed vector (CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:H) reflects that a privileged actor able to influence platform firmware or the device tree is required, which is considerably more restrictive than the published 8.4/PR:N rating. No public exploit code and no CISA KEV entry were identified at time of analysis, and no EPSS score was supplied.
Slot reset on IBM Z (s390) Linux kernel systems can hit the wrong PCI function, and the associated slot bookkeeping leaks memory, because the PCI core assigns a single shared pci_slot object to all functions of a multifunction device. Only s390 hosts running under a machine-level hypervisor with PCI pass-through are affected, and only when multifunction devices are exposed grouped into a shared PCI domain (the topology added by commit 44510d6fa0c0); the issue is local and requires a low-privileged authenticated actor able to drive the hotplug reset path (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H, base 8.4), with no confidentiality impact and no applicability to non-s390 architectures or s390 setups that still expose virtual functions as separate PCI domains. Vendor-released patches are available in the stable and mainline trees, and no public exploit code has been identified at time of analysis.
GitLab CE/EE 13.0 and later (before 19.1.8, 19.2.6 and 19.3.2) fails to properly validate group URL slugs during namespace transfers, allowing any authenticated user to induce a slug collision that leaves the legitimate owners of another group unable to modify that group's settings. The flaw is an availability-only issue (CVSS 4.3, C:N/I:N/A:L) rather than a data-disclosure or code-execution bug, but publicly available exploit detail exists via the linked HackerOne report, and the CWE-862 classification indicates the transfer workflow bypasses the authorization checks that should protect the target namespace. No CISA KEV listing or EPSS score was supplied, so active exploitation is not confirmed.
Improper authorization checks in GitLab CE/EE's Generic Package Registry (CWE-862) allow an authenticated user holding developer-role permissions to substitute the content of an existing package file and to hide packages from their legitimate owners. The flaw affects all GitLab Community and Enterprise Editions from 13.9 up to the fixed releases 19.1.8, 19.2.6 and 19.3.2, meaning the exposure window spans multiple major release lines and any long-lived install not patched in this cycle. Impact is integrity-only (CVSS 4.3, AV:N/PR:L/UI:N) - an attacker cannot read or delete data or crash the instance, but they can silently corrupt or conceal artifacts that downstream users and CI pipelines trust; publicly available exploit detail has been published via a HackerOne report.
Improper authorization controls in GitLab Enterprise Edition's compliance framework management allow an authenticated user holding the Security Manager role to execute arbitrary CI/CD jobs and reach protected CI/CD variables inside group projects. Affected are GitLab EE 18.11 through 19.1.7, 19.2.x before 19.2.6, and 19.3.x before 19.3.2, with fixes published in 19.1.8, 19.2.6, and 19.3.2. Exploit details are publicly available via a HackerOne report, and GitLab is credited as the reporter, though the issue is not listed in CISA KEV and no EPSS estimate was supplied.
Email can be delivered to an unintended, attacker-controlled domain by Nodemailer before 9.1.0, because the library's recipient normalizer encodes international domain names with a bundled raw RFC 3492 Punycode codec instead of applying UTS-46 mapping, so a domain that a standards-compliant validator folds to a trusted domain resolves to a different xn-- A-label at SMTP delivery time. The flaw is an interpretation conflict (CWE-436) reached over the network by unauthenticated senders (assessed CVSS:3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N, vendor CVSS:4.0 8.3), but exploitation is conditional: the consuming application must both allow-list, same-domain check, or user-confirm the recipient with a UTS-46/IDNA-conformant parser and then rely on Nodemailer to deliver to that already-approved address. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV; a vendor-released fix exists as Nodemailer 9.1.0.
Nodemailer versions 6.9.16 through 9.0.x mis-parse RFC 5322 comments inside recipient addresses, so a recipient written as 'user@good-corp.com(x)evil.com' is delivered by Nodemailer to 'good-corp.comevil.com' - a registrable domain an attacker can register - while a conformant RFC 5322 parser reads the domain as 'good-corp.com'. An unauthenticated remote attacker who can influence a recipient address can therefore reach a domain the sending application never approved, but only when the application makes its allow/deny decision on the domain using a strict RFC 5322 parser (without inspecting parse defects) or a naive prefix/substring allow-list and then hands the raw address to Nodemailer; the mis-parse propagates to both the SMTP envelope (RCPT TO) and the emitted To:/From: headers. This is a conditional, parser-disagreement issue assessed as Moderate (CVSS:3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N) despite the vendor-published CVSS 4.0 score of 8.3; no public exploit code has been identified at time of analysis and it is not listed in CISA KEV. Vendor-released patch: 9.1.0.
Unauthenticated adjacent attackers who can reach the sftunnel inter-device management channel can impersonate the peer device and register as an sftunnel peer on Cisco Secure Firewall Management Center (FMC) and Cisco Secure Firewall Threat Defense (FTD) Software, gaining manager-role privileges equivalent to root. Because the flaw is improper TLS certificate management in the protocol itself, default configurations are affected and no authentication or user interaction is required, but the attack only succeeds if the sftunnel connection is already down or can be disrupted long enough for the crafted-certificate handshake to complete (scored CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H, 8.3). No public exploit code has been identified at time of analysis and no EPSS score was supplied, so this is a serious, high-impact, but pre-exploitation issue that should be patched on a prioritized basis, especially where the FMC/FTD management plane is not isolated on a dedicated out-of-band network.
Improper authorization on the IODD file upload endpoint of multiple Pepperl+Fuchs ICE2 and ICE3 IO-Link master devices, as well as Phoenix Contact IOL MA8 PN DI8 units, permits any low-privileged authenticated remote user to upload IO-Link Device Description (IODD) files without the privilege level required for that operation. Successful exploitation can silently alter how connected IO-Link sensors and actuators are configured or interpreted by the master, or crash the device entirely by supplying malformed IODD content. No public exploit code and no CISA KEV listing have been identified at time of analysis.
Information disclosure in Craft CMS 5.0.0 through 5.10.12 can expose environment variables, secrets, database credentials, and other sensitive values when an independently occurring MySQL outage causes the application to treat the site as not installed. An unauthenticated attacker per the CVSS PR:N vector can reach anonymous installer actions such as install/validate-site if they previously obtained a valid guest session cookie and matching CSRF token and that session remains valid during the outage, then submit a predictable variable name and receive its expanded value. The flaw is gated by multiple stacked prerequisites, including an outage the attacker cannot induce and a pre-positioned valid session, and no public exploit identified at time of analysis; Craft CMS 5.10.13 contains the vendor fix.
Session-token forgery in the Cisco Secure Firewall Management Center (FMC) ASDM single sign-on handler lets an unauthenticated, remote attacker authenticate as the ASDM administrator user without any credentials or user interaction, and by repeating the forgery keep legitimate administrators locked out of ASDM indefinitely. The flaw stems from improper management of the ASDM SSO token (CWE-1259, improper restriction of security token inheritance), and it affects FMC releases across the 7.0.x through 7.7.x lines as well as 10.0.x per EUVD. No public exploit code or confirmed active exploitation has been identified at time of analysis, but the assessed impact is administrator account takeover and sustained denial of administrative access (CVSS 8.2, A:H, I:L), with the main practical barrier being network reachability to the FMC/ASDM management interface.
Local privilege escalation in Dell Update Package (DUP) Framework versions prior to 26.07.03 lets a low-privileged local user obtain elevated privileges when a Dell Update Package is executed through the affected framework. Exploitation is not autonomous: per the assessed vector (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H) it requires an already-authenticated low-privileged local account plus user interaction to trigger the vulnerable code path, and the impact crosses a security boundary (S:C) with high confidentiality, integrity and availability consequences. There is no public exploit identified at time of analysis and no indication of confirmed active exploitation; the issue is rated 8.2 High, making it a credible but not urgent local escalation risk that is fully closed by upgrading to 26.07.03 or later.
OAuth access-token theft in the rmcp Rust SDK (the official Rust SDK for the Model Context Protocol) before 2.0.0 allows a malicious MCP server to harvest a victim's legitimate bearer token by publishing RFC 9728 protected-resource metadata that names a different, legitimate MCP resource together with that resource's authorization server. The OAuth client transport never verifies that the returned `resource` identifier matches the MCP server URL it was actually configured to contact, so a victim who connects and completes the normal authorization/consent flow receives a genuine access token and then sends it to the attacker's endpoint, letting the attacker replay it against the legitimate MCP resource within the granted scopes. Exploitation requires the user to be induced to connect to the attacker-controlled server and to complete consent (UI:R; CVSS 3.1 vector AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N, SSVC Automatable=no), publicly available exploit code exists per the SSVC exploitation signal, and there is no CISA KEV entry confirming active exploitation.
Denial of service in the RabbitMQ amqp091-go Go AMQP 0.9.1 client affects all releases prior to 1.13.0: the library's frame-dispatch path synchronously pushes publisher confirms, flow-control events, consumer cancellations, returned messages and connection-block notifications into application-registered listener channels, so an unbuffered, undersized or not-promptly-drained listener channel permanently blocks the connection's sole reader goroutine. Once that goroutine stalls, the client stops processing incoming frames, acknowledgments, deliveries and heartbeats, which leads to connection stalls, missed heartbeats, deadlocks and eventual broker-initiated disconnection; exploitation requires a broker-driven burst of the corresponding events against an application that registered an affected listener, rather than any attacker-supplied payload. Unauthenticated remote triggering is possible per the published PR:N vector, but only applications built on versions below 1.13.0 that back a notification listener with a small or undrained channel are exposed, and no public exploit code has been identified at time of analysis. The issue is fixed in v1.13.0, where each notification send is bounded by a 5-second timeout and slow deliveries are dropped instead of blocking the reader.
Memory exhaustion in the RabbitMQ amqp091-go Go AMQP 0.9.1 client library prior to 1.13.0 lets unauthenticated remote attackers who can influence an application's Qos settings make the client request an absurdly large prefetch limit and then buffer enough broker-delivered messages to exhaust host memory. Channel.Qos performs no bounds validation, so a negative prefetchCount or prefetchSize is cast straight into the uint16/uint32 fields of the basic.qos method and wraps to 65535 or 4294967295 instead of being rejected. The vendor CVSS 4.0 score of 8.2 (High) is availability-only and materially gated by the attack requirement that the embedding application accept untrusted Qos values; default usage with hard-coded, non-negative values is unaffected, and no public exploit code was identified at time of analysis. The defect is repaired in 1.13.0 via a new validateQos check.
Heap memory corruption in the userspace SMB daemon of MikroTik RouterOS before 7.24 lets remote, unauthenticated attackers crash or destabilize the service by sending a crafted SMB1 SessionSetupAndX request whose uniPwdLen field triggers an integer underflow and an oversized copy into a smaller heap buffer (CWE-122). The independently assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) rates this as an availability-only impact - adjacent heap corruption in a userspace daemon, not a confirmed path to code execution - and the primary limiting factor is that the SMB service is not enabled by default on RouterOS. No public exploit code has been identified at time of analysis, and exploitation requires the SMB service to be enabled and network-reachable with legacy SMB1 dialect handling active; a vendor fix shipped in RouterOS 7.24.
An out-of-bounds write in Arista VeloCloud Edge and VeloCloud Gateway affects the VCMP tunnel protocol when it processes tunneled IP fragments, causing the affected process to crash and restart and briefly disrupting traffic on the affected SD-WAN node. Exploitation requires the attacker to already be an authenticated overlay neighbor with an established VCMP peer relationship to the target (assessed CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H) - internet hosts that are unauthenticated and cannot form an overlay peer relationship cannot reach the vulnerable logic. No public exploit code has been identified at time of analysis; the impact is bounded to a temporary availability loss, with no code execution or data compromise demonstrated.
Denial of service in the Linux kernel's NVMe-over-TCP (nvme-tcp) host driver, where nvme_tcp_handle_c2h_data() accepts a controller-to-host data PDU for a command that did not request a read; the receive path then hits WARN_ON_ONCE(i->data_source) inside _copy_to_iter(), returns -EFAULT, and resets the controller. The impacted component is the initiator side of the NVMe-oF TCP transport, so hosts are only at risk when they attach to a malicious or compromised NVMe-oF TCP target that can dictate PDU sequencing; there is no public exploit identified at time of analysis, and the practical severity is modest because the trigger requires control of the storage controller the host talks to (inverted trust model). Impact is normally limited to a failed command plus a controller reset, but on hosts booted with panic_on_warn the same warning becomes an immediate kernel panic and full system outage, which is the key amplifying condition behind the assigned A:H rating.
Unsigned client-side view state in the djust Python framework (pip/djust, versions before 1.0.7) is restored as trusted state on WebSocket reconnect, allowing an authenticated low-privileged user to tamper with the embedded state_json snapshot and inject arbitrary view attributes such as is_admin, account_id, or balance, achieving privilege escalation and business-state manipulation. The attack is network-reachable, requires no victim interaction, and yields high confidentiality and integrity impact (CVSS 3.1 base 8.1, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N), but only affects views that opt into the non-default state-snapshot feature and that store authorization or ownership data in public view attributes. The vendor released djust 1.0.7, which signs snapshots and rejects unsigned or forged snapshots on the back-navigation restore path; no public exploit code was identified at time of analysis and the flaw is not confirmed actively exploited (CISA KEV).
Multiple internally discovered incorrect-calculation flaws in Cisco Secure Firewall ASA Software, Secure Firewall Threat Defense (FTD) Software, and Secure Firewall Management Center (FMC) Software can be triggered by remote, unauthenticated attackers over the network and may result in high confidentiality, integrity, and availability impact across affected firewalls and their management plane. Cisco rates the group at CVSS 8.1 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), but the vector's AC:H reflects that exploitation depends on attacker-uncontrolled conditions - reliably producing the precise malformed input that causes the miscalculation is the practical barrier, and the bundled advisory names no single feature, protocol, or configuration toggle as a prerequisite. The flaws were found during Cisco's own internal hardening review, so there is no public exploit identified at time of analysis and no CISA KEV listing; remediation is delivered through Cisco's hardening release rather than awaiting out-of-band emergency fixes.
Improper authentication in Dell ObjectScale versions prior to 4.4.0.0 allows remote, unauthenticated attackers to bypass authentication and gain unauthorized access to the platform, with full impact to confidentiality, integrity, and availability (CVSS 3.1 8.1 High). The High attack complexity (AC:H) indicates exploitation requires satisfying a non-trivial precondition - such as a timing window or a specific system state in the authentication flow - rather than a single deterministic request, and no public exploit code has been identified at time of analysis. Only deployments running ObjectScale 4.4.0.0 and later are remediated, so older installations exposed on reachable management or S3 interfaces should be prioritized for upgrade.
Missing authorization enforcement in the Keycloak policy enforcer lets an authenticated user bypass path-based security policies in Red Hat Build of Keycloak and Red Hat Single Sign-On 7 deployments, gaining access to administrative or private application endpoints that the configured policies intended to protect. The flaw lies in how the enforcer normalizes request URLs containing encoded semicolons or directory-traversal segments, causing it to select a less restrictive policy than the one the backend application ultimately resolves to. Exploitation requires a valid account (even low-privileged), network reachability and an application deployed behind the policy enforcer using path-based authorization; no public exploit code was identified at time of analysis and the issue is not confirmed as actively exploited. Red Hat has published errata addressing the defect.
Client-side cross-site scripting in @nuxtjs/mdc before 0.22.1 allows attackers to execute arbitrary JavaScript in the page origin by smuggling executable URLs past the module's built-in Markdown sanitizer. Because parseMarkdown runs with allowDangerousHtml enabled by default and the sanitizer (validateProps/validateProp plus unsafeLinkPrefix) is the only defense, two sibling gaps are exploitable: an SVG anchor xlink:href (surfaced as the xLinkHref prop) carrying a javascript: URL, and an iframe src set to data:text/html that survives because the denylist compares url.protocol ('data:') rather than the full URL. The vendor rates this CVSS 8.1, the assessed vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N (unauthenticated per PR:N), and exploitation requires an application that renders attacker-controlled Markdown through the vulnerable versions. No CISA KEV listing or public exploit code was identified at time of analysis, though the fix PR (#491) and its regression tests publicly document both bypass payloads.
Authorization bypass in @fastify/auth versions 5.0.0 through 5.1.0 lets an authenticated low-privileged attacker who possesses a credential satisfying only the final member of a nested AND group, such as a valid API key without administrator rights, be authorized instead of rejected. The flaw occurs when strategies are composed with the relation "or" option together with the run "all" option and an entry is a nested array acting as an AND group, causing the group result to collapse to its last check; a mirror order-dependent bypass exists for top-level relation "and" with a nested "or" group. No public exploit identified at time of analysis, and there is no CISA KEV confirmation of active exploitation; the vendor-released fix is version 5.1.1 or later.
An out-of-bounds read in the Linux kernel's Wacom Bluetooth HID driver (wacom_intuos_pro2_bt_irq) allows an attacker in Bluetooth range who controls, spoofs, or merely operates a malfunctioning paired peripheral advertising a Wacom Intuos Pro/Intuos BT VID/PID to make the kernel parse a report shorter than the branch's fixed offsets, reading past the end of the received buffer. Because the driver force-registers pen, pad and touch input nodes for the matched device type via wacom_setup_device_quirks(), the leaked bytes are forwarded to userspace through evdev (MSC_SERIAL, ABS_MISC, ABS_WHEEL), giving a concrete confidentiality channel in addition to the immediate availability impact of a kernel OOB access on short descriptors. The reported CVSS is 8.1 (AV:A/AC:L/PR:N/UI:N), while our independent assessment rates it CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H - still adjacent and unauthenticated from a credential standpoint, but requiring the victim to pair/trust the hostile peripheral and, for any real confidentiality payoff, a local process consuming the evdev stream. No public exploit code was identified at time of analysis and there is no confirmed active exploitation (not CISA KEV); vendor patches are available in current stable trees.
A race condition in the Linux kernel's qla2xxx QLogic Fibre Channel driver allows a concurrent vport deallocation to free an NPIV virtual port while the format-1 report-ID-acquisition path still dereferences it, producing a use-after-free. The flaw is reachable only on systems that run a qla2xxx-driven QLogic FC HBA with NPIV virtual ports configured and that grant an attacker the local privilege needed to create and tear down virtual ports; the window is narrow (AC:H) and no attacker-controlled network input reaches the freed pointer, so the realistic outcome is a kernel crash or denial of service rather than controlled memory corruption. An independent assessment rates this CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H, notably lower than the published AV:N/PR:N vector, and no public exploit has been identified at time of analysis.
Use-after-free in the Linux kernel qla2xxx QLogic Fibre Channel SCSI driver lets a local user who can trigger queue-pair teardown reach freed request-queue memory through a late response-queue interrupt. On hosts with a QLogic FC HBA using MSI-X multiqueue qpairs, qla2xxx_delete_qpair() frees the request queue via qla25xx_free_req_que() before the response-queue IRQ is released in qla25xx_free_rsp_que(), so a response interrupt firing in that window causes qla2xxx_msix_rsp_q() to queue qpair->q_work and qla_do_work() -> qla24xx_process_response_queue() to dereference the now-freed rsp->req (LOGINOUT/CT/ELS entries and the status path). The result is full memory corruption with high confidentiality, integrity, and availability impact, but exploitation requires winning a narrow local race during qpair deletion; no public exploit code or active exploitation was identified at time of analysis, and vendor patches are available.
Code injection into the quay-builder-qemu release workflow through supply-chain compromise of the third-party GitHub Action `Noelware/docker-manifest-action`, which the workflow references by a mutable branch instead of a pinned immutable commit SHA. An attacker who first subverts that upstream action can execute arbitrary code inside the release pipeline, exfiltrating sensitive registry credentials or publishing malicious container images, with severity amplified because the workflow also exposes the default GITHUB_TOKEN. This is a CI/CD build-pipeline flaw rather than a defect in deployed Quay instances and is not directly exploitable against Quay itself; no public exploit code was identified at time of analysis, and the assessed vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H reflects high attack complexity because successful exploitation depends on first compromising an external dependency and only triggers when the release workflow executes.
Stored cross-site scripting in the Jenkins OWASP Dependency-Check Plugin 5.6.4 and earlier allows an authenticated user holding the Item/Configure permission to inject script into the Jenkins UI by way of CWE values that are rendered from Dependency-Check reports without escaping; the payload persists in the stored report and fires only when a victim later loads the affected report page (UI:R), so no unauthenticated or anonymous path exists. No public exploit code has been identified at time of analysis, and the plugin is not listed in CISA KEV, so this is not confirmed actively exploited. Independent assessment rates this as a moderate-priority stored XSS rather than a top-tier emergency despite the 8.0 vendor score, since successful abuse requires a non-trivial job-configuration privilege, depends on a second user viewing the crafted report, and caps out at limited confidentiality and integrity impact (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N).
Stored cross-site scripting in Jenkins Coverage Plugin 3.3358.v9487dde48783 and earlier lets an attacker who already holds Item/Configure permission on a job submit a job configuration through the REST API with a javascript: scheme URL in the unvalidated coverage results ID field, which is then stored and rendered when a victim later opens the job's coverage page. Exploitation therefore requires authenticated low-privilege access (CVSS PR:L) plus victim interaction (UI:R), meaning it is not usable against default unauthenticated Jenkins deployments; Impact on confidentiality, integrity and availability is rated High (CVSS 8.0). No public exploit code or confirmed active exploitation was identified at time of analysis, and CISA's SSVC assessment records Exploitation: none and Automatable: no.
Stored cross-site scripting in Jenkins Warnings Plugin 13.10258.va_17d49a_78c3b_ and earlier lets an authenticated attacker holding Item/Configure permission inject a javascript: scheme value as the analysis results identifier by submitting a job configuration through the REST API, bypassing the validation that the normal UI path performs. The payload is persisted with the job and executes in the browser of any user who later opens the affected Warnings/analysis results page (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H, 8.0, CWE-79). No public exploit code has been identified at time of analysis, and CISA SSVC rates exploitation as none and automatable as no, although technical impact is rated total; vendor patches are available in 13.10259.v80f407cb_03a_e and the backport 13.10223.10225.vcf001b_b_b_3a_90.
Arbitrary code execution in Jenkins Script Security Plugin 1415.v9a_f9b_3a_c253d and earlier: when a user with job-configure privileges defines classpath entries in an item configuration, those entries are silently auto-approved the moment a user holding Overall/Administer permission copies that item or updates its configuration through the REST API or CLI. The result is code execution inside the Jenkins controller JVM (CWE-94, CVSS 8.0), but exploitation is a two-actor, confused-deputy scenario: the attacker needs pre-existing config-edit rights (PR:L) and must wait for a privileged user to perform the copy or API/CLI update (UI:R), so installations where only administrators author jobs and never copy them or drive configuration through REST/CLI are effectively unexposed. No public exploit code or confirmed active exploitation was identified at time of analysis.