info1 source
A newly unveiled White House accord aimed at artificial intelligence development has drawn widespread skepticism over its lack of formal enforcement mechanisms.
Signed alongside an executive order by President Donald Trump, the agreement instructs the federal government to retire terms like "artificial intelligence" and "AI" in favor of "super intelligence" or "SI." The document was signed by tech leaders across the industry, including the chief executives of OpenAI, Anthropic, Google, Meta, X, and hardware giant Nvidia.
The framework urges participating frontier AI companies to implement a four-step safety process centered around internal controls, internal oversight, and independent external reviews that report directly to corporate boards of directors.
However, policy analysts have pointed out that the document lacks promissory commitments, instead employing normative phrasing such as "companies should" rather than legally binding pledges.
While critics argue that self-regulation has historically failed to curb technological risks and digital harms, proponents suggest that voluntary frameworks establish baseline standards of reasonable care while formal legislative processes remain stalled in Congress.
Read more → about White House AI Accord Relies on Voluntary Self-Policing Amid Regulatory Pushbackhigh1 sourceCVE-2026-71963 CVE-2026-72718
Researchers at Manifold Security disclosed a vulnerability class dubbed GitSpawn that affects multiple AI-powered developer tools, including Claude Code, Cursor, OpenAI Codex, Goose, Hermes Agent, Grok Build, and Qwen Code.
The issue stems from how coding agents automatically gather repository context on launch by executing background commands like `git status` or `git diff` before receiving user input or establishing workspace trust boundaries.
When a developer opens a project directory pre-populated with a `.git` folder, the local repository configuration dictates how Git executes certain features.
The primary attack vector leverages Git's legitimate `core.fsmonitor` configuration, which is designed to call external helper utilities to optimize file-change monitoring in massive codebases.
Because the automated agents run background Git commands without first sanitizing local repository settings, Git parses the attacker-supplied `core.fsmonitor` value and executes the specified executable on the host system.
The resulting payload runs with the developer's logged-in permissions, completely bypassing standard AI sandboxing and prompt-based confirmation dialogues.
Standard operations like `git clone` or `git pull` do not carry local repository configuration files, meaning attacks rely on direct directory transfers like ZIP archives, shared storage drives, or sync folders.
Researchers identified eight distinct vulnerabilities across the affected agents, observing that the spawned processes run entirely in the background without UI alerts or user interaction.
Remediation has begun across the industry, with Goose patching CVE-2026-72718 in version 1.44.0 and Claude Code addressing its `core.fsmonitor` vector in version 2.1.196 alongside fixes for Cursor and Codex.
However, several products remained vulnerable at disclosure time, including Hermes Agent (CVE-2026-71963) in version 0.21.0, Grok Build version 1.0.13, Qwen Code version 0.22.3, and an additional unpatched `ultrareview` configuration execution sink in Claude Code.
Read more → about GitSpawn Flaw in AI Coding Agents Executes Malicious Commands via Git Configurationscritical1 source
OpenAI has officially placed its latest model, Astra, into the 'Critical' cybersecurity capability tier under its internal Preparedness Framework. This internal classification marks the first time an OpenAI model has crossed this threshold, which triggers mandatory additional safeguards prior to any public deployment.
According to OpenAI's internal risk definitions, the critical designation is reserved for systems capable of autonomously discovering and weaponizing zero-day flaws across defended environments, or executing end-to-end attacks on hardened infrastructure given only high-level prompts. During standardized testing, Astra secured a 100% score on the ExploitBench evaluation suite, which measures an engine's proficiency in converting published security advisories into functional exploits.
In separate live assessments targeting newly disclosed vulnerabilities, the model independently identified two novel zero-day flaws without human assistance. Astra also successfully performed a sandbox breakout from a web browser to execute local system commands on the host machine. Furthermore, the model autonomously chained multiple distinct vulnerabilities across a hardened operating system configuration to escalate privileges directly to root access.
On the alignment front, OpenAI claims Astra rejected 91.5% of cyber-related jailbreak attempts during testing, a measurable jump from the 59% refusal rate recorded on its predecessor, GPT-5.6 Sol. Evaluators also noted that the system showed a reduced propensity to probe deliberately introduced honeypots or subvert system instructions. Consequently, full access to Astra's raw offensive capabilities will remain restricted to select testing cohorts initially before rolling out under the Daybreak Blue program.
Read more → about OpenAI classifies new Astra model as Critical risk after automated zero-day discovery and sandbox escapes