F´ (F Prime) is a framework that enables development and deployment of spaceflight and other embedded software applications. Prior to version 4.2.0, the bounds check byteOffset + dataSize > fileSize uses U32 addition that wraps around on overflow. An attacker-crafted DataPacket with byteOffset=0xFFFFFF9C and dataSize=100 overflows to 0, bypassing the check entirely. The subsequent file write proceeds at the original ~4GB offset. Additionally, Svc/FileUplink/File.cpp:20-31 performs no sanitization on the destination file path. Combined, these allow writing arbitrary data to any file at any offset. The impact is arbitrary file write leading to remote code execution on embedded targets. Note that this is a logic bug. ASAN does not detect it because all memory accesses are within valid buffers — the corruption occurs in file I/O. Version 4.2.0 contains a patch. No known workarounds are available.
CVE-2026-34082 is a medium severity vulnerability in the open-source LLM app development platform Dify (langgenius). Before version 1.13.1, the DELETE API endpoint for removing conversations lacks proper authorization checks, allowing any authenticated user to delete chat histories belonging to other users. This issue is fixed in version 1.13.1. The vulnerability is classified under CWE-863 (Incorrect Authorization) and CWE-284 (Improper Access Control).
OpenHarness before commit bd4df81 contains a server-side request forgery vulnerability in the web_fetch and web_search tools that allows attackers to access private and localhost HTTP services by manipulating tool parameters without proper validation of target addresses. Attackers can influence an agent session to invoke these tools against loopback, RFC1918, link-local, or other non-public addresses to read response bodies from local development services, cloud metadata endpoints, admin panels, or other private HTTP services reachable from the victim host.
In spring 2022, a highly sophisticated backdoor named AngrySpark was discovered on a single machine in the United Kingdom. The malware employed a three-stage architecture: a DLL masquerading as a Windows Task Scheduler component, a custom virtual machine interpreter running bytecode instructions, and a beacon that profiles systems while disguising C2 communications as PNG image requests. The malware featured VM-based obfuscation, dual encrypted C2 channels using RSA-4096 and XXTEA encryption, direct syscalls bypassing usermode hooks, hypervisor detection, and CET-aware anti-analysis capabilities. It operated for approximately one year with active maintenance visible through syscall table updates and configuration changes between May 2022 and January 2023. The infrastructure expired in mid-2023 and the operation ceased, with no additional samples or victims identified despite the significant engineering effort invested in its development.
Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language.
Security Fix(es):
* brace-expansion: brace-expansion: Denial of Service via unbounded brace range expansion (CVE-2026-25547)
* minimatch: minimatch: Denial of Service via specially crafted glob patterns (CVE-2026-26996)
* minimatch: Minimatch: Denial of Service via catastrophic backtracking in glob expressions (CVE-2026-27904)
* undici: undici: Denial of Service via unbounded memory consumption during WebSocket permessage-deflate decompression (CVE-2026-1526)
* undici: Undici: Denial of Service via invalid WebSocket permessage-deflate extension parameter (CVE-2026-2229)
* undici: Undici: HTTP Request Smuggling and Denial of Service due to duplicate Content-Length headers (CVE-2026-1525)
* undici: undici: Denial of Service via crafted WebSocket frame with large length (CVE-2026-1528)
* nghttp2: nghttp2: Denial of Service via malformed HTTP/2 frames after session termination (CVE-2026-27135)
* Node.js: Node.js: Denial of Service due to crafted HTTP `__proto__` header (CVE-2026-21710)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
A Code Injection and Missing Authentication vulnerability in Google Agent Development Kit (ADK) versions 1.7.0 (and 2.0.0a1) through 1.28.1 (and 2.0.0a2) on Python (OSS), Cloud Run, and GKE allows an unauthenticated remote attacker to execute arbitrary code on the server hosting the ADK instance.
This vulnerability was patched in versions 1.28.1 and 2.0.0a2.
Customers need to redeploy the upgraded ADK to their production environments. In addition, if they are running ADK Web locally, they also need to upgrade their local instance.
On March 19, a researcher on X posted a suspicious Android APK tied to a phishing page impersonating Paidy, a Japanese buy-now-pay-later service. A quick look at the infrastructure behind it revealed an unauthenticated API sitting wide open, with endpoints exposing payloads, command logs, and the C2 source code itself. The server wasn't running a simple credential harvester. Agents for Android, iOS, Windows, Linux, and macOS were present, alongside a canvas-based device fingerprinting system and code that references iOS sandboxing mechanisms by name. The actor behind it is clearly comfortable with Japanese, and large portions of the codebase show signs of LLM-assisted development.
### Summary
[`server.fs`](https://vite.dev/config/server-options#server-fs-strict) check was not enforced to the `fetchModule` method that is exposed in Vite dev server's WebSocket.
### Impact
Only apps that match the following conditions are affected:
- explicitly exposes the Vite dev server to the network (using `--host` or [`server.host` config option](https://vitejs.dev/config/server-options.html#server-host))
- WebSocket is not disabled by `server.ws: false`
Arbitrary files on the server (development machine, CI environment, container, etc.) can be exposed.
### Details
If it is possible to connect to the Vite dev server’s WebSocket **without an `Origin` header**, an attacker can invoke `fetchModule` via the custom WebSocket event `vite:invoke` and combine `file://...` with `?raw` (or `?inline`) to retrieve the contents of arbitrary files on the server as a JavaScript string (e.g., `export default "..."`).
The access control enforced in the HTTP request path (such as `server.fs.allow`) is not applied to this WebSocket-based execution path.
### PoC
1. Start the dev server on the target
Example (used during validation with this repository):
```bash
pnpm -C playground/alias exec vite --host 0.0.0.0 --port 5173
```
2. Confirm that access is blocked via the HTTP path (example: arbitrary file)
```bash
curl -i 'http://localhost:5173/@fs/etc/passwd?raw'
```
Result: `403 Restricted` (outside the allow list)
<img width="3898" height="1014" alt="image" src="https://github.com/user-attachments/assets/f6593377-549c-45d7-b562-5c19833438af" />
3. Confirm that the same file can be retrieved via the WebSocket path
By connecting to the HMR WebSocket without an `Origin` header and sending a `vite:invoke` request that calls `fetchModule` with a `file://...` URL and `?raw`, the file contents are returned as a JavaScript module.
<img width="1049" height="296" alt="image" src="https://github.com/user-attachments/assets/af969f7b-d34e-4af4-8adb-5e2b83b31972" />
<img width="1382" height="955" alt="image" src="https://github.com/user-attachments/assets/6a230d2e-197a-4c9c-b373-d0129756d5d7" />
A hacker named Jonathan Spalletta exploited vulnerabilities in the smart contracts of the Uranium cryptocurrency exchange, stealing approximately $55 million in cryptocurrency. This attack forced the Uranium exchange to shut down operations. The exploitation targeted flaws in the exchange's smart contract code, allowing unauthorized access to funds. Although no specific affected versions or CVEs are listed, the incident highlights risks inherent in smart contract security. The attack did not require user interaction but leveraged weaknesses in contract logic. There is no indication of widespread exploitation beyond this event. The medium severity rating reflects significant financial loss but limited broader systemic impact. Organizations relying on smart contracts for financial transactions should review their code for similar vulnerabilities. Countries with significant cryptocurrency adoption and blockchain development are most at risk. Immediate mitigation involves thorough smart contract audits and implementing best practices for secure contract development.
The Axios NPM package was compromised through a supply chain attack attributed to North Korean threat actors. Attackers exploited a long-lived NPM access token to bypass GitHub Actions' OIDC-based CI/CD publishing workflow, enabling them to push backdoored versions of the package. This breach allows malicious code to be distributed to developers and applications relying on Axios, a widely used HTTP client library in JavaScript environments. Although no known exploits in the wild have been reported yet, the potential for widespread impact exists due to Axios's extensive use in web and mobile applications. The attack highlights vulnerabilities in CI/CD pipeline security and token management. Mitigation requires immediate revocation of compromised tokens, strengthening CI/CD authentication mechanisms, and vigilant monitoring of package integrity. Countries with significant software development sectors and heavy reliance on JavaScript ecosystems, including the United States, India, Germany, South Korea, Japan, and the United Kingdom, are most at risk. Given the ease of exploitation and potential for supply chain compromise, the severity is assessed as high despite the current low severity rating. Defenders must prioritize securing CI/CD workflows and verifying package authenticity to prevent similar attacks.
A critical vulnerability was discovered in OpenAI Codex that could allow attackers to compromise GitHub tokens. This flaw potentially enables unauthorized access to sensitive GitHub credentials, which could lead to repository manipulation, data theft, or further lateral movement within affected environments. Although no known exploits have been observed in the wild, the severity is critical due to the sensitive nature of GitHub tokens and the potential impact on confidentiality and integrity. The vulnerability does not specify affected versions or patches, indicating a need for immediate investigation and mitigation by organizations using OpenAI Codex integrated with GitHub workflows. Defenders should prioritize reviewing token management practices and monitor for unusual access patterns. Countries with significant technology sectors and heavy use of GitHub and AI coding tools are at higher risk. Immediate mitigation steps include restricting token scopes, rotating tokens, and applying any forthcoming patches or updates from OpenAI or GitHub. This threat highlights the importance of securing AI-assisted development environments and credential management.
baserCMS is a website development framework. Prior to version 5.2.3, a path traversal vulnerability exists in the theme file management API (/baser/api/admin/bc-theme-file/theme_files/add.json) that allows arbitrary file write. An authenticated administrator can include ../ sequences in the path parameter to create a PHP file in an arbitrary directory outside the theme directory, which may result in remote code execution (RCE). This issue has been patched in version 5.2.3.
baserCMS is a website development framework. Prior to version 5.2.3, there is an OS command injection vulnerability in the update functionality. Due to this issue, an authenticated user with administrator privileges in baserCMS can execute arbitrary OS commands on the server with the privileges of the user account running baserCMS. This issue has been patched in version 5.2.3.
Red Hat OpenShift Dev Spaces provides a cloud developer workspace server and a browser-based IDE built for teams and organizations. Dev Spaces runs in OpenShift and is well-suited for container-based development.
The 3.27 release is based on Eclipse Che 7.115 and uses the DevWorkspace engine to provide support for workspaces based on devfile v2.1 and v2.2.
Users still using the v1 standard should migrate as soon as possible.
https://devfile.io/docs/2.2.0/migrating-to-devfile-v2
Dev Spaces supports OpenShift EUS releases v4.16 and higher. Users are expected to update to supported OpenShift releases in order to continue to get Dev Spaces updates.
https://access.redhat.com/support/policy/updates/openshift#crw
KEY FINDINGS AI-assisted malware development has reached operational maturity.VoidLink framework, which is modular, professionally engineered, and fully functional,was built by a single developer using a commercial AI-powered IDE within a compressedtimeframe. AI-assisted development is no longer experimental but produces deploymentreadyoutput. AI-assisted development is not always obvious from the final product.VoidLink was initially assessed as the […] The post AI Threat Landscape Digest January-February 2026 appeared first on Check Point Research .
