Security Digest: March 25, 2026 - 26 Critical Vulnerabilities

Today's security landscape is marked by 26 critical vulnerabilities that demand immediate attention. Among these, issues in npm n8n and composer wwbn/avideo pose the highest risk.

· 3 min read

Executive Summary

Today's security landscape is marked by 26 critical vulnerabilities that demand immediate attention. Among these, issues in npm n8n and composer wwbn/avideo pose the highest risk, potentially leading to unauthorized data access and remote code execution. Immediate patching and mitigation steps are essential to safeguard your systems.

Critical Vulnerabilities

  • CVE-2026-33663: Unauthorized Access to HTTP Credentials in n8n
    • Impact: Attackers can steal plaintext HTTP credentials.
    • Affected Systems: n8n Community Edition, versions prior to 1.123.27, 2.13.3, 2.14.1.
    • Immediate Action: Upgrade to the latest patched version.
    • Mitigation: Restrict access to trusted users and audit credentials.
  • CVE-2026-33660: Remote Code Execution via Merge Node in n8n
    • Impact: Potential unauthorized file access and code execution.
    • Affected Systems: n8n versions before 2.14.1, 2.13.3, 1.123.27.
    • Immediate Action: Upgrade immediately, disable Merge node.
    • Mitigation: Limit workflow editing permissions.
  • CVE-2026-33669: Arbitrary File Read in SiYuan
    • Impact: Unauthorized document access.
    • Affected Systems: SiYuan using vulnerable API endpoints.
    • Immediate Action: Restrict API access and monitor logs for suspicious activity.
  • CVE-2026-33716: Live Stream Control Bypass in AVideo
    • Impact: Full control over live streams without authentication.
    • Affected Systems: AVideo with vulnerable live stream plugins.
    • Immediate Action: Apply recommended code change to remove `streamerURL` parameter override.

What to Do Now

  1. Immediately upgrade all affected systems to the latest versions as specified above.
  2. Apply configuration changes and disable problematic features where immediate upgrades are not possible.
  3. Verify system integrity and check logs for any signs of exploitation.
  4. Implement monitoring for any anomalous activities, particularly around API endpoints and credential access.

Related Resources

Keep reading