<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with log4shell]]></title><description><![CDATA[A list of topics that have been tagged with log4shell]]></description><link>https://board.circlewithadot.net/tags/log4shell</link><generator>RSS for Node</generator><lastBuildDate>Mon, 06 Apr 2026 07:54:08 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/tags/log4shell.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[🤖 Tool: MEDUSA — AI-first Security Scanner]]></title><description><![CDATA[---------------- Tool: MEDUSA — AI-first Security ScannerOverviewMEDUSA is presented as an AI-first security scanner with more than 9,600 detection patterns focused on AI/ML applications, LLM agents, RAG pipelines, MCP servers and traditional codebases. The release v2026.5.0 emphasizes AI supply-chain coverage with a new Git scanning capability and repo poisoning detection.Key technical facts• Detection surface: 9,600+ AI security patterns targeting agent frameworks, MCP protocols, RAG components and editor/IDE config files.  • CVE coverage: Product claims detection of 133 CVEs, with named detections including Log4Shell, Spring4Shell, XZ Utils backdoor, LangChain RCE, MCP remote code execution and React2Shell.  • New rules: v2026.5.0 adds 45 attack rules for repo poisoning and 11 rules for MCP advanced attacks (schema poisoning, sampling injection, cross-server manipulation, Flowise RCE).  • Repo poisoning specifics: Detection across 28+ AI editor and IDE file types (examples enumerated include Cursor, Cline, Copilot, Claude Code, Gemini CLI, Kiro, Codex CLI, Windsurf, Amazon Q, Roo Code).  • Performance &amp; outputs: Parallel processing for multi-core scanning, smart caching to skip unchanged files, and multiple export formats (JSON, HTML, Markdown, SARIF).Technical implications (reporting the release)The release documents a focused effort on AI supply-chain tactics: repo poisoning heuristics, editor-config weaponization, and MCP-targeted attack rules. The product adds path-relative FP filtering to reduce false positives when repo names previously matched heuristics. The Git scanning feature is described as a single-step repo analysis for supply-chain indicators.Constraints and scopeThe documentation frames MEDUSA as cross-platform (Windows/macOS/Linux) with IDE integrations and optional linter enhancements. The release notes list capabilities and detection counts; they do not provide operational deployment commands or step‑by‑step setup details. medusa #ai_security #repo_poisoning #log4shell #langchain Source: https://github.com/Pantheon-Security/medusa]]></description><link>https://board.circlewithadot.net/topic/ade763a5-e460-4195-b93a-11997e36b569/tool-medusa-ai-first-security-scanner</link><guid isPermaLink="true">https://board.circlewithadot.net/topic/ade763a5-e460-4195-b93a-11997e36b569/tool-medusa-ai-first-security-scanner</guid><dc:creator><![CDATA[hasamba@infosec.exchange]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>