baserCMS is a website development framework. Starting in version 5.0.0-beta1 and prior to versions 5.3.2 and 5.4.2, `PermissionGroupsService::build()` reads a plugin's `config/permission.php` to decide what each user group may reach. When that file is absent it writes a wildcard allow rule instead: `url` `/baser/<prefix>/<plugin>/*`, `method` `*`, `auth` true, for every non-admin group. BcCustomContent has no such file in any release. After an administrator installs it, the default `operators` group can store and execute arbitrary PHP under the document root. Versions 5.3.2 and 5.4.2 patch the issue.
baserCMS versions 5.2.5 before 5.3.2 and 5.4.0 before 5.4.2 contain an improper input validation vulnerability in public mail forms. An unauthenticated visitor can supply a comma-separated list of email addresses in the email field, causing a single auto-reply to be sent to multiple third parties. This occurs when server-side VALID_EMAIL validation is not enabled on newly created forms with email-type fields. The bundled contact form is not affected as it enables VALID_EMAIL validation by default. The issue has been fixed in versions 5.3.2 and 5.4.2.
Hidden functionality (undocumented backdoor) in the root-privileged 'assistant' daemon in DJI CrystalSky ZS600C firmware v0.3.9.7 through v0.6.6.9 on Android allows a physically-present attacker with USB access to execute arbitrary OS commands as root by sending the hard-coded magic string 'dji26656677' to the USB-gadget serial interface (/dev/ttyGS0), after which each subsequent line is passed to system().
A hostname canonicalization vulnerability in the email HTML sanitizers of Zimbra Collaboration Suite (ZCS) allows an unauthenticated sender to bypass the restriction on forms that target the Zimbra host. DefangFilter and the OWASP ActionAttributePolicy compare the form-action hostname with the request hostname before browser URL canonicalization. A percent-encoded hostname can therefore survive sanitization while the browser submits the form to the normal Zimbra origin with the recipient's authentication cookie. This permits authenticated form requests from a crafted email after the recipient opens it in Classic and submits the form. The issue is present in ZCS 10.1.16 and 10.1.21. It does not bypass an endpoint's CSRF-token checks; a state-changing attack additionally requires an endpoint that accepts the resulting request without that protection.
An organizer authentication vulnerability in Zimbra Collaboration Suite (ZCS) allows an unauthenticated email sender to insert calendar invitations attributed to another user. The email delivery path permits external invitations but does not verify that the message sender is authorized to use the iCalendar ORGANIZER identity. When automatic invitation insertion is enabled, a crafted REQUEST component creates an event containing attacker-selected meeting details and reminders under a forged organizer without recipient interaction. No corresponding event is created in the claimed organizer's calendar. ZCS 10.1.16 and 10.1.21 are affected.
An attendee authentication vulnerability in the email calendar processing of Zimbra Collaboration Suite (ZCS) allows an unauthenticated sender to forge another attendee's response to an existing meeting. Zimbra passes a null sender identity when processing iCalendar REPLY components, causing the attendee authorization filter to be skipped. An attacker who knows the meeting UID, organizer address and attendee address can send a non-outdated reply that changes the attendee's participation status in the organizer's calendar. The change occurs automatically during delivery without organizer or attendee interaction. ZCS 10.1.16 and 10.1.21 are affected.
An organizer authentication vulnerability in the email calendar processing of Zimbra Collaboration Suite (ZCS) allows an unauthenticated sender to cancel or modify an existing meeting in a recipient's calendar. Zimbra accepts iCalendar CANCEL and REQUEST components without verifying that the email sender is authorized to act as the supplied organizer. An attacker who knows the meeting UID and organizer address can supply a non-outdated sequence number to move the recipient's meeting to Trash or replace its details. Processing occurs automatically during email delivery without recipient interaction. ZCS 10.1.16 and 10.1.21 are affected.
CVE-2026-55606 is a buffer over-read vulnerability in the odhcpd DHCPv6 server component used by OpenWrt. In versions 25.12 and earlier, the DHCPv6 self-loop detection code uses a network-byte-order DUID length value directly as the memcmp() size parameter, causing memcmp() to read beyond the allocated stack buffer on little-endian systems. This vulnerability can be triggered by a single unauthenticated DHCPv6 packet, resulting in a 2560-byte overread from a 128-byte buffer. No patches are publicly available at the time of publication.
A critical stack-based buffer overflow vulnerability exists in the odhcpd DHCPv6 IA response handler used by OpenWrt. Versions prior to 25.12 are affected. The flaw allows writing beyond a fixed 512-byte stack buffer when processing DHCPv6 REQUEST packets with many IA options. The vulnerability is reachable remotely via unauthenticated UDP packets and runs with root privileges. This can lead to remote code execution, especially on embedded devices lacking typical memory protections. The issue has been fixed in OpenWrt version 25.12.
odhcpd is the DHCPv6, DHCPv4, and router-advertisement server used by OpenWrt. From version 17.01.0 to before version 25.12.3, odhcpd's DHCPv6 IA parser accepts an IA_NA or IA_PD option whose body is shorter than struct dhcpv6_ia_hdr, casts the option header to that full structure, and reads ia->iaid before proving that the IA body contains the IAID field. If an unauthenticated network-adjacent client places a zero-length or otherwise short IA option at the end of odhcpd's 8192-byte receive stack buffer, the IAID read crosses from data_buf into adjacent stack memory. The disclosed bytes are then reflected in the DHCPv6 reply IAID; prior ARM validation showed data_buf[8192:8196] disclosing the saved stack canary, and wider stack scans can leak ASLR-useful stack/process contents. This issue has been patched in version 25.12.3.
CVE-2026-53918 is a use-after-free vulnerability in the odhcpd DHCPv6 handler used by OpenWrt. It affects versions prior to 25.12 and involves a dangling pointer when processing multiple IA options in a DHCPv6 message, leading to a heap-use-after-free read. This can cause unauthenticated denial of service and confusion of DHCPv6 Reconfigure/ForceRenew keys. The issue has been patched in version 25.12.
A request attribute override vulnerability in Zimbra Collaboration Suite (ZCS) allows unauthenticated requests to /h/* to populate servlet attributes intended for trusted internal dispatch. RestFilter copies URL parameters specifying an authentication token, target account, target item and dispatch state into the request attributes consumed by the Classic Web Client. Combined with CVE-2026-10632 on ZCS 10.1.16, this allows an attacker to supply their own valid token and document identifiers and execute JavaScript in another user's signed-in browser session. ZCS 10.1.17 blocks that XSS chain by changing the document renderer, but retains the request attribute override.
serialize-javascript from 7.0.1 before 7.1.3 contains a cross-site scripting vulnerability that allows attackers to break out of HTML script elements by ending serialized function source text with an unescaped </script. Attackers controlling a function's source via a spoofed toString() can combine surrounding output delimiters and later values to inject live markup such as img onerror handlers.
Aokigahara is a newly observed infostealer malware that targets a wide range of sensitive data on Windows systems. It steals traditional credentials such as browser passwords, cookies, cryptocurrency wallets, VPN and FTP client data, email profiles, and password manager files. Uniquely, it also targets AI applications and developer tools including Claude, ChatGPT Desktop, Codex, Cursor, Windsurf, GitHub Copilot, and Gemini CLI, collecting authentication files, session tokens, and configuration data. The malware additionally targets cloud environment credentials for AWS, Azure, and Google Cloud, as well as developer environment secrets like Git credentials and SSH private keys. Stolen AI and cloud credentials could enable unauthorized access to paid AI services, cloud resources, and source code repositories. The malware includes capabilities such as screenshot capture, clipboard theft, and a clipper component for cryptocurrency manipulation. There is no confirmed information on how the stolen data is monetized. No patch or remediation guidance is provided.
SignalK signalk-server versions from 2.28.0-beta.2 up to but not including 2.34.0 contain a server-side request forgery (SSRF) vulnerability. This flaw exists in the App Store icon fetcher component, which trusts absolute URLs for signalk.appIcon. An attacker can publish npm packages with Signal K keywords that cause the server to make requests to internal or cloud metadata endpoints. The responses, if image-typed, are then stored and served back via the admin UI. The vulnerability has a low CVSS 4.0 score of 2.3 and does not have known exploits in the wild.
Agentfront mcp-from-openapi versions from 2.2.0 up to but not including 2.9.0 contain a server-side request forgery (SSRF) vulnerability. This flaw allows attackers to bypass the denylist of blocked hosts by appending a trailing dot to hostnames, enabling unauthorized requests to operator-blocked hosts. The vulnerability arises from incomplete filtering of disallowed inputs in the OpenAPI specification URL or redirect targets.
A vulnerability in agentfront's mcp-from-openapi versions 2.5.0 up to but not including 2.9.0 allows attackers to capture Authorization and Cookie headers. This occurs because the safeFetch() function forwards these sensitive headers on cross-origin redirects, enabling attackers controlling a spec host or exploiting an open redirect to steal bearer tokens or cookies.
hydra-ray-launcher 1.1.0.dev1 before 1.2.2 and 1.4.0.dev4 before 1.4.0rc2 contains an arbitrary module import vulnerability via the ray_pkg_version OmegaConf resolver passing input to importlib.import_module(). Attackers controlling configuration values or command-line overrides can supply a ray_pkg_version interpolation to import any installed module, triggering its import-time side effects in the application process.
A PHP vulnerability was recently disclosed with coordinated patches released by PHP.net and many vendors. No reliable public exploit code is currently available, though some firms claim to have working exploits. Cloudflare and Amazon report many exploit attempts, but it is unclear if these are effective. Applying the official patches is the recommended defense. Workarounds and web application firewall rules may provide limited temporary protection. Embedded devices and appliances running vulnerable PHP versions are a concern due to patching difficulties and should be isolated. The situation highlights the importance of timely patching and preparedness for future similar vulnerabilities.
Heimdall versions prior to 0.17.17 improperly validate client IP addresses extracted from Forwarded and X-Forwarded-For headers when the trusted_proxies option is enabled. This allows arbitrary, malformed, or obfuscated IP values to be accepted and processed. The Forwarded header parser also incorrectly splits quoted strings, causing parsing errors. This vulnerability has been fixed in version 0.17.17.