AI Governance Engineer is an open, versioned body of knowledge that maps AI governance frameworks such as the EU AI Act, ISO 42001, and NIST AI RMF to concrete artefacts satisfying each obligation. It provides a structured approach to AI governance engineering, emphasizing continuous, machine-readable evidence over point-in-time attestations. The resource includes chapters, a maturity model, reusable patterns, and data exports to support implementation and auditability of AI governance obligations.
A potential compromise of the OWASP API Security website (https://api-security.owasp.org/) has been reported via a Reddit post. The page currently displays a responsible disclosure notice from NOX Offensive Security indicating a vulnerability affecting the organization and requesting secure contact for further details. No sensitive technical details or exploit information are publicly disclosed at this time.
The ShinyHunters extortion group hacked and defaced the Clop (Cl0p) ransomware operation's data leak site by exploiting an unauthenticated file upload vulnerability in Grav CMS. They replaced the site content with their own messages and ASCII art, claiming to have stolen server data including source code, Grav CMS plugins, system logs, and private keys for Clop's Tor onion service. ShinyHunters threatened to extort Clop, demanding payment within 72 hours. This attack appears to be part of an ongoing feud between the two cybercrime groups, with ShinyHunters retaliating against threats made by Clop representatives. The incident raises questions about a potential shift in ransomware group dynamics toward direct attacks on rival groups. No independent verification of the full extent of data theft has been confirmed.
A file collision bug in the PcapSplitter library causes silent packet loss when TCP sessions reuse the same 5-tuple, resulting in file truncation or corruption. This occurs because the filename generation is based only on IP and port, causing multiple sessions to overwrite the same output file. The issue was identified during PCAP processing and fixed by suffixing filenames only on actual collisions. The bug led to fewer packets being written than reported, with no error exit codes, making detection difficult.
A security researcher named Gal Weizman disclosed a browser security research achievement involving a single browser extension that successfully exploited vulnerabilities in Chrome, Comet, Edge, Opera, and Claude in Chrome. This research led to the discovery of two CVEs and earned $20,000 in bounty rewards from multiple major vendors including Anthropic, Perplexity, Google, Microsoft, and Opera. No detailed technical information or affected versions are provided.
Reports indicate that TikTok users' cameras have been hacked using an open weight AI model developed by a group named depthfirst. The claim is based on a news article discussing how free AI software is enhancing hacker capabilities. No technical details, affected versions, or confirmed exploits are provided in the available information.
This content announces the soft reopening of the r/Darktrace subreddit community for discussions related to the Darktrace product and company. The subreddit was previously restricted and is now being moderated to allow more users while controlling spam and activity levels.
This content compares four AI-based vulnerability scanners—Codex, Mythos, Aikido, and Audn—using the OWASP Juice Shop as a testbed. It is a discussion post on Reddit Cybersecurity sharing a link to an external artifact that evaluates these tools. No specific vulnerability or exploit is described.
This content describes a research study survey targeting small-business information security professionals in the United States to assess their absorptive capacity in facing AI-driven threats. It is a call for participation in an academic study and does not describe a specific security vulnerability or threat.
A suspicious URL (https://xysrx.com/PV.js) was found embedded below the closing HTML tag on the homepage of a website serving Clickfix. The JavaScript code fetched from this URL collects visitor environment data such as theme preference, timezone, screen resolution, and browser automation status, encodes this data, and conditionally injects additional HTML content triggered by user interactions like mouse clicks. This behavior suggests potential unauthorized content injection or tracking. No official vendor advisory or patch information is available.
Brevo disclosed a supply-chain attack involving a compromised Cloudflare API key that was used to inject malicious scripts into over 100,000 websites using Brevo services. The attack highlights risks from trusted third-party infrastructure and embedded scripts, emphasizing the security challenges posed by API keys and SaaS dependencies. This incident underscores the need to evaluate trust boundaries with vendors integrated into applications.
AI agents that rely on MCP (Model-Controller-Plugin) tool descriptions trust these descriptions similarly to how browsers trust TLS certificates. Attackers have begun exploiting this trust by poisoning tool metadata, which can lead to unauthorized actions such as secret exfiltration and silent email BCCs. This attack surface is not widely covered by existing security tools. The threat involves manipulating tool descriptions dynamically to alter agent behavior post-integration. The recommended defensive approach is to treat tool descriptions as untrusted input and implement measures such as pinning, hashing, and baseline comparisons to detect unauthorized changes.
This content describes a student's academic project formalizing the Security Operations Center (SOC) monitoring and response loop as a set of mathematical axioms. The project, named Algebraic Security for Monitoring and Response (ASMR), proposes a formal framework to model the entire security monitoring pipeline from system state through observation, decision, and action. It is a draft manuscript with no validation against real data yet and is intended as a theoretical foundation rather than a practical security tool or vulnerability.
This advisory highlights a security risk where AI agents with misconfigured permissions can access enterprise data beyond what the querying user is authorized to see. A user unable to access Salesforce directly was able to retrieve Salesforce data through a Microsoft Copilot AI agent with broader permissions. This creates a form of privilege escalation via AI agents, potentially exposing sensitive information without triggering traditional access control events. The advisory emphasizes the need for entitlement-parity reviews and integration of identity and cloud audit data to detect and mitigate such risks.
This report discusses the challenge of detecting lateral movement attacks in corporate networks using behavior baselines built from observed history. The key issue is that the baseline can become 'poisoned' by the intrusion itself, causing the attack to blend into what the system considers normal behavior over time. The analysis is based on experiments using synthetic training data and real authentication logs from Los Alamos National Laboratory. The findings highlight limitations of detection methods relying solely on historical baselines and emphasize the need for carefully managed baseline update windows to balance detection accuracy and staleness.
This report discusses the limitations of AI code review tools that rely solely on comments in pull requests (PRs) to flag security issues. Comments from automated tools often blend into the noise of multiple bot messages and are frequently ignored or skimmed over, leading to security issues being merged without proper attention. The authors highlight a real example where sensitive information was exposed before authorization checks, which might have been missed if only commented on. Their solution is to fail the GitHub check itself for issues above a severity threshold, preventing merges until fixed, and providing instant fixes. This approach aims to increase the visibility and enforcement of security findings in code reviews.
This content discusses key enterprise security controls for managing MCP (Model Communication Protocol) usage in organizations. MCP enables AI agents to interact with business tools, expanding AI capabilities but increasing attack surface and risk. The main security controls recommended are ensuring all AI actions are attributable to a human user, enforcing least privilege for AI agents, and routing all MCP requests through a governed middleware gateway that enforces business policies. The gateway can require human approval for high-risk actions, throttle bulk reads, screen inbound content, and audit all activity. This approach mitigates risks such as unauthorized destructive actions, data exfiltration via prompt injection, and shadow MCP usage. The discussion is advisory and does not describe a specific vulnerability or exploit.
SLDP (Simple Layer-2 Discovery Protocol) is a lightweight, stateless Layer-2 bootstrapping protocol designed to automate discovery between IPv4-only and IPv6-only devices on a common broadcast domain. It operates directly over Ethernet frames without requiring IP stack initialization and is intended as a commissioning tool rather than a runtime protocol. SLDP uses a dedicated EtherType and a two-step handshake to establish MAC-to-IP mappings, facilitating integration in mixed IPv4/IPv6 environments such as industrial IoT and legacy networks. It is not a replacement for ARP, NDP, or LLDP and runs only on demand during device commissioning. The protocol includes a security blueprint (CLL Trust Oracle) to protect against address spoofing during discovery. No known exploits or vulnerabilities have been reported, and no patch or remediation is applicable as this is a newly proposed protocol.
This content is a Reddit post requesting participation in a survey for thesis work, containing a link to a Qualtrics survey form. There is no indication of a security threat, vulnerability, or malicious activity associated with this request.
CISA will discontinue its Weekly Vulnerability Bulletin at the end of fiscal year 2026 (September 28, 2026) to transition from severity-based vulnerability management to risk-based vulnerability prioritization. Vulnerability information will continue to be accessible via CVE.org, the Known Exploited Vulnerability (KEV) Catalog, CISA Cybersecurity Alerts and Advisories, and vendor security alerts. This change reflects evolving vulnerability management strategies in response to the increasing volume of CVEs driven by AI-assisted research.