The http.cookiejar.CookieJar component improperly deleted stored cookies when receiving a response with an already expired Set-Cookie header. This deletion occurred without consulting the cookie policy, allowing a server to potentially delete cookies from other domains within a shared cookie jar, such as urllib's HTTPCookieProcessor. The issue was fixed by ensuring the cookie policy is checked before allowing an expired cookie to delete an existing one, in compliance with RFC 6265 section 5.3.
CVE-2026-82115 is a missing authorization vulnerability in Apache Wicket's native WebSocket support. The WebSocketMessageBroadcastHandler delivers incoming frames to shared WebSocket resources without consulting the configured authorization strategy, allowing unauthorized callers with a valid session and resource name to invoke resource callbacks. This affects Apache Wicket versions from 8.0.0 through 8.19.0, 9.0.0 through 9.24.0, and 10.0.0 through 10.11.0. The issue is fixed in versions 8.20.0, 9.25.0, and 10.12.0.
Botan is a C++ cryptography library. From 3.7.0 until 3.13.0, an application that calls AutoSeeded_RNG::clear() and then calls randomize with an empty output buffer while the generator is unseeded can cause AutoSeeded_RNG to mark itself seeded without consulting the configured entropy source. On builds without BOTAN_HAS_SYSTEM_RNG, the fallback uses only a clock value and process ID, so a later non-empty request can produce output from predictable state. This issue is fixed in version 3.13.0.
CVE-2026-15586 is a vulnerability in İdvlabs Software and Consulting Services Inc.'s Ontime product that allows brute force attacks due to improper restriction of excessive authentication attempts. The issue affects versions up to and including 2026-10-27. The vendor was contacted but did not respond to the disclosure. The CVSS score is 5.3, indicating a medium severity vulnerability.
CVE-2026-105947 is a path traversal vulnerability in Innotim Software's Logsign SIEM affecting versions from 6.4.120 up to but not including 6.4.122. This flaw allows an attacker with low privileges to access files outside the intended directory, potentially exposing sensitive information. The vulnerability has a medium severity with a CVSS score of 6.5. A fix is available in version 6.4.122.
A vulnerability in Pillow's libtiff encoder allows crafted TIFF files to cause memory disclosure or process crashes during TIFF re-saving. The flaw arises from a mismatch between Pillow's argument passing to libtiff's TIFFSetField() and libtiff's internal tag definitions, leading to reading unintended memory or segfaults. This occurs when Pillow forwards unrecognized TIFF tags from the source file without properly consulting libtiff's field table. The issue affects applications that open and then save TIFF images, especially when metadata is preserved. No out-of-bounds writes were observed, only reads. The vulnerability was introduced in Pillow 5.4.0 and affects versions from 0.86.1_1 onward as per the provided data.
Grav 2.0.0 through 2.0.24 contain a Twig content sandbox escape. The `array` filter (and its identical function form) is on the sandbox allowlist but is registered without the needs_is_sandboxed guard that print_r, vardump, json_encode, yaml_encode and string carry, and its implementation calls toArray() — or falls back to an (array) cast — without consulting the sandbox method allowlist. Because the `grav` Twig global is the raw Pimple-based dependency injection container, a user who can author Twig in page content can evaluate `grav|array` to read the container's private $values array, including the un-redacted Config service; a second array cast returns the entire configuration tree, disclosing plugin credentials, SMTP and OAuth secrets, Redis passwords, proxy URLs and the security.* subtree that the sandbox's redaction is meant to hide. Because the payload is stored in page content, the disclosed configuration is rendered to anonymous visitors. Grav 1.7 is not affected as it has no Twig content sandbox. Fixed in Grav 2.0.25.
A vulnerability in the Linux kernel's HID wacom driver (CVE-2026-89999) allows out-of-bounds reads due to improper validation of report length in the wacom_intuos_pro2_bt_irq function. The driver parses Bluetooth reports without consulting the actual report length, leading to potential reading beyond the buffer when a malicious or spoofed Bluetooth peripheral sends an undersized report. This can cause out-of-bounds memory reads that are forwarded to userspace via evdev input nodes. The issue affects specific Linux Azure kernel versions.
The Consulting theme for WordPress is vulnerable to Privilege Escalation in versions up to, and including, 6.7.16. This is due to a combination of two flaws: (1) the masterstudy_ms_stm_set_discard_transient AJAX endpoint in admin/admin-notices/classes/STMHandler.php accepts an arbitrary transient key without capability checks or nonce validation, and (2) the developer access login mechanism in admin/classes/stm-theme-support.php authenticates users based on a transient value without proper cryptographic validation when in legacy string mode. This makes it possible for authenticated attackers, with subscriber-level access and above, to set the stm_developer_access_token transient to a known value (1), then authenticate as any existing user including administrators by visiting a specially crafted URL, thereby achieving full privilege escalation to administrator.
Description
The Logviewer offers `logs.users` and `logs.groups` so operators can control who may read log content. For
daemon logs those settings were not applied: the access decision combined the "this is a daemon log" flag
with the authorizer result in a way that discarded the authorizer's answer whenever the flag was set, and
the daemon log page and download endpoints reached the handler without consulting an authorizer at all. Any
user able to pass the configured servlet filter could therefore read `nimbus.log`, `supervisor.log` and the
other daemon logs on every reachable node, which contain other tenants' topology names, owners and
configuration fragments.
The same advisory covers the log listing endpoints, which accepted a user argument and never applied it, so
`/listLogs` and `/searchLogs` returned every tenant's topology and worker log file names regardless of the
caller. That part is metadata only.
There was no configuration that closed either behaviour.
Mitigation
Upgrade to 3.1.0, where the daemon log paths evaluate the same configured user and group lists that the
worker log paths already used, and the listing endpoints filter by the requesting user.
Users who cannot upgrade immediately should place the Logviewer behind a reverse proxy that restricts the
daemon log endpoints, and should treat daemon log content as readable by any filter-authenticated user.
Credit
The ASF -- found using Claude agents to study the security of open-source projects, validated and reported by Apache Storm.
The BlueMoon exploit kit chains together three zero-day vulnerabilities—two in Chrome's V8 engine and one in Windows ALPC—to achieve sandbox escape and privilege escalation. Initially used by the China-linked APT Violet Typhoon, it has rapidly proliferated among multiple espionage-motivated threat actors targeting NGOs, aerospace, manufacturing, government, consulting, and financial sectors across the US and Southeast Asia. The vulnerabilities in Chrome were patched on September 3 and 8, 2026, and the Windows privilege escalation was fixed in the September 2026 Patch Tuesday update. BlueMoon's rapid adoption and sharing among threat actors may reflect lowered barriers to exploit development, potentially aided by AI. The exploit kit downloads and executes payloads after successful exploitation.
An open redirect vulnerability (CWE-601) exists in the Library Information and Document Automation Program by Yordam Informatics Technology Consulting, Training, and Electronic Systems Industry and Trade Inc. This vulnerability affects versions from 22.1 up to but not including 22.2. It allows attackers to craft URLs that redirect users to untrusted external sites, which can facilitate phishing attacks. The vulnerability has a CVSS 3.1 base score of 6.1 (medium severity). No official patch or remediation information is currently available.
A Server-Side Request Forgery (SSRF) vulnerability exists in Yordam Informatics Technology Consulting's Library Information and Document Automation Program versions before 22.2. This vulnerability allows an attacker to induce the server to make unintended requests. The flaw has a CVSS 3.1 base score of 5.3, indicating medium severity. The issue is fixed in version 22.2.
CVE-2026-11838 is a vulnerability in the Library Reservation System by Yordam Informatics Technology Consulting that involves missing authentication for a critical function, allowing input data manipulation. It affects versions before 22.2. The vulnerability has a medium severity with a CVSS score of 4.3. A fix is available in version 22.2.
CVE-2026-82586 is a high-severity vulnerability in ash-project's ash_lua component that allows Lua scripts to bypass field exposure restrictions. The vulnerability arises because the read operation in AshLua.Runtime resolves field names without consulting the exposed-field allow-list, enabling scripts to read any attribute, including private sensitive fields like hashed passwords. This affects versions from 0.1.0 up to but not including 0.2.1.