Ariquo Security News Stream — 2026-11-21
52 daily news events from 89 source observations.
Vulnerabilities & patches
Etherpad: Pre-auth arbitrary file read
Published:
An unauthenticated path‑traversal / arbitrary file read vulnerability in Etherpad's /static/* handler allows any remote, unauthenticated user to read any file on the server's filesystem (e.g. GET /static/plugins/ep_etherpad-lite/static/..%5C..%5C..%5C..%5C..%5C..%5C..%5Cetc/passwd returns /etc/passwd) available to the user running the etherpad software. Because the endpoint is mounted before the authentication middleware, no credentials, session, or configuration change are required.
amqtt: 2 security advisories
Published:
GitHub published 2 security advisories affecting amqtt. Reported issues include: aMQTT: Denial of Service (DoS) via Memory Leak in Unmanaged QoS 2 Session Handshakes; aMQTT: Inefficient Regular Expression Complexity and Uncontrolled Resource Consumption and Improper Input Validation.
basercms: 2 security advisories
Published:
GitHub published 2 security advisories affecting basercms. Reported issues include: baserCMS administrative API authorization bypass through session fallback; baserCMS: Path Traversal Bypass via realpath() in BcThemeFileService (CVE-2026-30940 Patch Bypass).
flyto-core: 3 security advisories
Published:
GitHub published 3 security advisories affecting flyto-core. Reported issues include: Flyto2 Core: http.paginate follows server-supplied next-page URLs (Link header / cursor) without SSRF revalidation; Flyto2 Core: SSRF guard validates the resolved IP but connects by hostname, allowing DNS-rebinding TOCTOU; Flyto2 Core: Arbitrary file write via unguarded data.*/file.* modules (incomplete fix of CVE-2026-67429).
Sources · 3
daptin: 2 security advisories
Published:
GitHub published 2 security advisories affecting daptin. Reported issues include: Daptin: Broken Access Control (IDOR) in the generic YJS collaboration endpoint; Daptin: Unauthenticated SQL Injection via the `sort` query parameter on every entity list endpoint.
Chinese-nexus actor’s Cairn AI agents found a zero-day on their own | AWS Security Blog
Published:
Amazon Threat Intelligence is sharing findings from an investigation into a Chinese-nexus threat actor using autonomous AI agents to conduct hacking operations with minimal human involvement. The actor gave the agents a simple goal: “obtain shell access.” During the campaign, the agents found a zero-day in an open-source application and used it to gain full control of a server.
Java4Shell and the NGINX HTTP/2 Patched with DHI
Published:
OpenJDK and Oracle disclosed Java4Shell (CVE-2026-114938) on November 17, and NGINX released fixes for two HTTP/2 flaws the next day. Docker began publishing fixed images for both in the Docker Hardened Images (DHI) catalog starting that same day.
nginx2root: five new nginx vulnerabilities, and how Cloudflare protects origins from the worst of them | Cloudflare Blog
Published:
On November 18, 2026, F5 and nginx.org disclosed ten vulnerabilities in nginx. Five of them, detailed by the Xint research team and published under the name nginx2root, are memory corruption flaws that an unauthenticated attacker can use to crash an nginx worker or, per Xint's research, run commands on the server.
refitter: 2 security advisories
Published:
GitHub published 2 security advisories affecting refitter. Reported issues include: Refitter allows arbitrary code execution through unescaped OpenAPI content-type values; Refitter allows arbitrary code execution through unescaped OpenAPI paths.
Java4Shell (CVE-2026-114938): What It Means for TeamCity - The JetBrains Blog
Published:
On November 17, 2026, CVE-2026-114938, a memory-corruption vulnerability in the hardware-accelerated Base64 decoder of several Java runtimes, was publicly disclosed. This vulnerability allows malicious Base64 input to corrupt JVM process memory, potentially causing a crash or remote code execution.
Sources · 4
WhatsApp Fixes Flaw Uncovered While Disrupting Scam Campaign - SecurityWeek
Published:
Asked by SecurityWeek about the exploitation, a WhatsApp spokesperson said, “Our team found this issue while disrupting a scam campaign, and we believe a scammer was using it to make their scam message seem more credible.”
Sources · 4