Bi-Weekly April 24, 2026

Threat Intel Bi-Weekly — April 24, 2026

Coverage: April 22–24, 2026  ·  CVEs & Exploits, AI & Supply Chain, Threat Actors, Dark Web

6
Total Findings
5
High
1
Medium
1
AI CVEs
2
CISA KEV
Coverage: April 22 – 24, 2026  ·  Sources: NVD, CISA KEV, Exploit-DB, Mandiant, CrowdStrike, HaveIBeenPwned, The Hacker News, SentinelOne, GitHub Security Advisories

CVEs & Exploits

3 findings
High
JetBrains TeamCity Path Traversal — Actively Exploited, CISA KEV
CVE-2024-27199  ·  CISA KEV  ·  Unauthenticated path traversal
An unauthenticated path traversal vulnerability in JetBrains TeamCity CI/CD server is being actively exploited in the wild. CISA added it to the Known Exploited Vulnerabilities catalog. Attackers are using the flaw to read sensitive configuration files — including agent authentication tokens and internal API credentials — without requiring any login. The vulnerability affects TeamCity versions prior to 2023.11.4.
Remediation
Upgrade TeamCity to 2023.11.4 or later immediately. If an immediate upgrade is not possible, restrict TeamCity server access to the internal network only — do not expose it to the internet. After patching, rotate all agent tokens and review build logs for signs of unauthorized access or exfiltrated secrets. Check CISA KEV for the mandatory federal remediation deadline.
Action: Upgrade TeamCity to 2023.11.4+, rotate agent tokens, restrict external access.
High
Apache ActiveMQ RCE via Jolokia Bridge
CVE-2026-34197  ·  Affects <5.19.4 and 6.0.0–6.2.2  ·  Patched: 5.19.4 / 6.2.3
A remote code execution vulnerability exists in Apache ActiveMQ's Jolokia JMX-HTTP bridge. An attacker with network access to the Jolokia endpoint can invoke arbitrary MBean operations to execute code on the broker host. The Jolokia interface is enabled by default in many ActiveMQ deployments and is often inadvertently exposed. Affects all ActiveMQ versions below 5.19.4 and the 6.0.0–6.2.2 range.
Remediation
Upgrade to Apache ActiveMQ 5.19.4 or 6.2.3. If upgrade is not immediately possible: disable the Jolokia agent by removing activemq-web-console.war or setting jolokia.enabled=false in the ActiveMQ configuration. Restrict access to the Jolokia endpoint (port 8161 by default) to trusted management hosts only via firewall rules.
Action: Upgrade ActiveMQ to 5.19.4 / 6.2.3 or disable Jolokia immediately.
High
CrowdStrike LogScale Unauthenticated Path Traversal
CVE-2026-40050  ·  SaaS: auto-patched  ·  Self-hosted: manual patch required
An unauthenticated path traversal vulnerability in CrowdStrike LogScale (Humio) allows an attacker to read arbitrary files from the server filesystem. CrowdStrike's SaaS-hosted instances were automatically patched. However, organizations running self-hosted LogScale clusters must apply the patch manually. The vulnerability can expose log data, configuration files, and internal credentials stored on the LogScale host.
Remediation
SaaS customers: no action required — patched automatically. Self-hosted customers: apply the patch from the CrowdStrike Security Advisories page immediately. After patching, audit filesystem permissions on the LogScale host to limit exposure. Restrict LogScale cluster endpoints to internal network access only.
Action: Self-hosted LogScale only — apply patch from CrowdStrike advisory portal.

AI & Supply Chain

2 findings
High
Axios npm Compromise — Sapphire Sleet (DPRK) RAT Deployment
Threat Actor: Sapphire Sleet (DPRK)  ·  Malicious: axios@1.14.1, axios@0.30.4  ·  CISA KEV adjacent
North Korean threat actor Sapphire Sleet published malicious versions of the widely-used axios npm package (versions 1.14.1 and 0.30.4) bundled with plain-crypto-js@4.2.1 which installs a Remote Access Trojan. These typosquat or version-hijack packages blend in with legitimate axios installs and establish persistent C2 channels. Any developer whose environment ran npm install axios during the window these packages were live is potentially compromised.
Remediation
Check your lock files: grep -r "axios" package-lock.json — verify the resolved version is the legitimate one (check the official axios npm registry checksum). Run npm audit across all projects. If axios@1.14.1 or 0.30.4 was installed, treat the development machine as compromised: rotate all secrets, tokens, and SSH keys stored on that machine. Review outbound network connections for C2 activity to unknown IP ranges.
Action: Audit lock files for malicious axios versions, rotate all secrets if found.
High
GitHub Copilot VS Code Extension — Command Injection
CVE-2026-23653  ·  CVSS: Pending  ·  Tool: GitHub Copilot (VS Code)
A command injection vulnerability in the GitHub Copilot VS Code extension allows a malicious repository to craft inputs that escape the extension's shell invocation context and execute arbitrary commands in the developer's local environment. The flaw is triggered when Copilot processes certain inline code suggestions from a repository containing specially crafted comments or docstrings. CVSS score is pending official assignment.
Remediation
Update the GitHub Copilot VS Code extension to the latest version via the Extensions marketplace (Ctrl+Shift+X → search Copilot → Update). Do not open untrusted repositories with Copilot enabled until patched. Monitor the NVD entry for CVSS assignment and additional details.
Action: Update GitHub Copilot VS Code extension immediately.

Threat Actors & Dark Web

1 finding
High
Vercel / Context.ai OAuth Supply Chain Breach via Lumma Stealer
Actor: Lumma Stealer (initial access broker)  ·  Scope: Vercel developer accounts
Attackers used Lumma Stealer malware to harvest OAuth tokens from developers' machines, then leveraged those tokens to gain lateral access to Vercel projects and Context.ai integrations. The breach exposed deployment tokens, environment variable secrets, and in some cases production API keys stored in Vercel project settings. The attack chain demonstrates how credential-stealing malware targeting developer endpoints can propagate into production infrastructure via OAuth trust relationships.
Remediation
Revoke all Vercel OAuth tokens and re-authenticate. Audit all OAuth app authorizations connected to your GitHub/Vercel accounts — revoke any apps you don't recognize or no longer use. Rotate all environment variables and secrets stored in Vercel. Enable endpoint detection on developer machines to catch stealer malware (Lumma Stealer targets browser credential stores). Enable Vercel audit logging and review for unauthorized access.
Action: Revoke Vercel OAuth tokens, rotate all env secrets, audit OAuth app grants.

Priority Action Matrix

// biggest risk this period
Axios DPRK RAT + Copilot CVE = developer toolchain is the dominant attack surface.
The combination of a nation-state supply chain attack targeting the most-downloaded HTTP library in npm (axios) and an unpatched command injection flaw in GitHub Copilot means the developer environment itself is the primary threat vector this period. Attackers no longer need to breach production infrastructure — they're compromising developers directly, then pivoting to production through CI/CD pipelines, OAuth grants, and deployment tokens.