CVE-2026-115731 is a critical remote code execution vulnerability in Perforce Puppet that allows clients with any CA-signed agent certificate to execute code on the server. The flaw arises from deserialization of untrusted data in Puppet's report processing, enabling malicious payload execution with service user permissions. Exploitation can lead to exposure of the server's certificate-signing key, issuance of trusted certificates by attackers, and unauthorized changes to managed systems. The vulnerability was patched in Puppet Enterprise versions 2026.0.1, 2025.12.1, 2023.8.13, and Puppet Core versions 9.1.3 and 8.22.2. It has been actively exploited in the wild and is listed in CISA's Known Exploited Vulnerabilities catalog.
Axence nVision versions prior to 18 transmit user authentication tokens via HTTP GET request query parameters. This practice exposes tokens to interception or leakage through logs or network monitoring. An attacker who obtains a valid token can impersonate the user and perform unauthorized actions. The vulnerability is identified as CWE-598 and has a CVSS 4.0 base score of 6.3 (medium severity). The issue was fixed in version 18.
MISP contains an authorization bypass vulnerability in the SharingGroup model's captureSGExisting method. This flaw allows users with the sync permission to bypass membership checks and gain unauthorized read access to restricted sharing groups. Exploitation requires an authenticated sync user who knows a valid sharing group UUID. The attacker can modify sharing group records to add their organization as a member, exposing sensitive threat intelligence data. The vulnerability affects MISP versions up to 2.5.51 and has a medium severity rating.
In Eclipse Mosquitto versions 2.1.0 to 2.1.2, the mosquitto_ctrl utility would crash if attempting to interact with a hostile broker and the broker sent a non-string "error" value.
In Eclipse Mosquitto versions 2.1 through 2.1.2, a listener configured with `protocol websockets` mishandles empty WebSocket data frames. `net__read_ws()` in `lib/net_ws.c` returns the number of framing bytes consumed (the 4 masking-key bytes) for a data frame with a zero-length payload, without writing any bytes to the caller’s buffer. The MQTT packet reader in `packet__read_single()` (`lib/packet_mosq.c`) trusts that return value as a payload byte count. A remote client can therefore advance the read position over an uninitialised heap allocation, causing the broker to process and forward uninitialised heap memory (information disclosure, including heap and libc pointers), and can underflow the unsigned `to_process` counter so that subsequent attacker-controlled frame data is written past the end of the allocation (heap out-of-bounds write). The out-of-bounds write is reachable from the CONNECT packet before any authentication check, so an unauthenticated client can corrupt the heap and crash the broker even when `allow_anonymous false` is set. Combining the disclosure and the write allows remote code execution as the broker’s user by any client able to establish a session.
CVE-2026-132049 is a moderate severity vulnerability in the lldpd service on Red Hat Enterprise Linux 10. The flaw involves an out-of-bounds read when parsing LLDP-MED location records due to improper length verification. An adjacent attacker on the local network can exploit this by sending crafted packets, potentially causing information disclosure of adjacent process memory. The lldpd daemon itself is not disrupted, and the default client lldpcli is not affected. The vulnerability only impacts custom applications using the liblldpctl library without prior length checks. The lldpd service is optional and not enabled by default in Red Hat Enterprise Linux 10. No patch or mitigation is currently available that meets Red Hat's criteria for deployment and stability.
In Eclipse Mosquitto versions 2.1.0 to 2.1.2, a broker with a listener that is configured to use the PROXY protocol v2 is vulnerable to an untrusted proxy providing details that cause the broker to accept fake SSL information.
This can be mitigated by following the documented requirements for PROXY listeners: It is very important that only trusted proxies are allowed to connect to any listener using the PROXY protocol, and that clients are not allowed to connect to the listener at all.
A vulnerability in Phoenix Contact FL SWITCH, FL NAT, and FL WLAN devices allows an unauthenticated remote attacker positioned between the RADIUS client and server to forge authentication responses. This could enable unauthorized administrative access to the affected devices.
Multiple vulnerabilities in Phoenix Contact FL SWITCH, FL NAT, and FL WLAN devices allow unauthenticated remote attackers to execute arbitrary code. Exploitation can lead to full compromise of the device, impacting confidentiality, integrity, and availability.
A privilege escalation vulnerability exists in the firmware of Phoenix Contact FL WLAN 23xx and FL WLAN 2x1x devices. Exploitation allows an attacker to gain full administrative access, resulting in complete loss of confidentiality, integrity, and availability of the affected device.
Eclipse Mosquitto versions 2.0.0 to 2.0.22 and 2.1.0 to 2.1.2 contain a vulnerability where the return values of password hash functions (sha512-pbkdf2 and legacy sha512) are not checked. Due to changes in OpenSSL 4.0, sha512-pbkdf2 hashing fails with the FIPS provider for passwords shorter than 8 characters, causing newly created passwords under 8 characters to match any other password of the same length.
CVE-2026-112213 is an out-of-bounds read vulnerability in the pixReadMemJp2kCore() function of the Leptonica library. The flaw arises because the function uses the output dimensions of the first image component to iterate buffers of all components, which can lead to reading beyond the bounds of smaller component buffers allocated by OpenJPEG. This can cause adjacent memory data to be included in the decoded image pixels, potentially disclosing information to anyone accessing the output.
Insufficient Session Expiration vulnerability in the Apache Iggy server HTTP transport. A self-issued JSON Web Token (JWT) identified the user only by numeric user ID, and a new user takes the lowest free ID. After an administrator deleted a user, that user's unexpired token, or a token refreshed from it while the ID was free, authenticated as the next account created with that ID and had that account's permissions. Only deployments with HTTP enabled are affected.
This issue affects Apache Iggy: through 0.9.0.
Users are recommended to upgrade to version 0.10.0, which fixes the issue.
Missing Authorization vulnerability in the Apache Iggy server. The system snapshot command (GetSnapshot on the binary transports and POST /snapshot on HTTP) checked only that the caller was logged in, not the read_servers or manage_servers permission. Any authenticated user, including a user with no permissions, could download a diagnostic archive with the server log files, the host process list, a file system listing and the runtime server configuration. The runtime configuration contains the HTTP JWT signing secret and the message encryption key when they are set in the configuration. If HTTP is enabled, the user could use the signing secret to create tokens for any account, including root.
This issue affects Apache Iggy: before 0.9.0.
Users are recommended to upgrade to version 0.10.0, which fixes the issue.
In Eclipse versions 1.5-1.6.13, 2.0.0-2.0.22 and 2.1.0-2.1.2, the client library libmosquitto does not reject Will messages with payloads greater than 65535 bytes when calling `mosquitto_will_set()` or `mosquitto_will_set_v5()`. This results in up to 65535 bytes of uninitialised heap memory being transmitted as the Will.
This can be mitigated by only passing payloads with a maximum length of 65535 bytes.
In the Apache Airflow Microsoft Azure provider 10.2.0 through 15.3.0, `S3ToAzureBlobStorageOperator` turned off TLS certificate verification for its connection to Amazon S3 by default (`s3_verify=False`), whatever the AWS connection's own verification settings were. An attacker positioned on the network between an Airflow worker and S3 could intercept that traffic, read the signed requests and alter the listed object keys and the copied file contents. Deployments are affected when a Dag uses `S3ToAzureBlobStorageOperator` without setting `s3_verify`. Users are advised to upgrade to apache-airflow-providers-microsoft-azure 15.3.1 or later, which uses the AWS connection's verification settings by default.
CVE-2026-19707 is a critical heap-based buffer overflow vulnerability in Airlock Gateway versions 8.5.2 and earlier, and 8.6.0. The flaw arises when the Smart Form Protection feature processes attacker-controlled HTML in backend responses containing certain multi-byte HTML character references. Successful exploitation can lead to denial of service or remote code execution on the Airlock Gateway, potentially impacting the availability and security of other backends behind the gateway. The vulnerability is fixed in versions 8.5.3 and 8.6.1.
A vulnerability in the Linux kernel ALSA usx2y driver involves uninitialized idle URB pointers before submitting USB audio streams. This can lead to a null pointer dereference and a kernel crash (general protection fault) during stream startup.
A concurrency issue in the Linux kernel ALSA hwdep interface allows multiple DSP load requests for the same index to proceed simultaneously, violating assumptions about firmware loading. This can cause warnings and potential double allocation of resources in affected drivers such as snd-usb-usx2y.
A vulnerability in the Linux kernel ALSA usx2y driver allows a retried DSP load request after a failure to proceed improperly, potentially causing kernel warnings and instability. The issue arises when certain initialization functions fail but previously allocated URBs remain, leading to assertion failures on retry attempts. The fix marks the chip as hung to refuse retried requests, preserving system stability.