I have been thinking a lot about AI and integrity. Part of that is contextual integrity. I recently found two papers on the topic. “CIMemories: A Compositional Benchmark for Contextual Integrity of Persistent Memory in LLMs“: Abstract: Large Language Models (LLMs) increasingly use persistent memory from past interactions to enhance personalization and task performance. However, this memory introdu

Large Language Models (LLMs) that utilize persistent memory for personalization and task enhancement face significant risks concerning the inappropriate disclosure of sensitive information, a problem identified as a challenge to "contextual integrity." This issue becomes more pronounced as LLMs are increasingly deployed as autonomous agents making decisions on behalf of users.
Recent research highlights the difficulty LLMs have in controlling information flow from their memory based on the specific context of a task. A benchmark called CIMemories was developed to evaluate this problem, using synthetic user profiles with over 100 attributes per user and diverse task contexts where each attribute's relevance varies.
Evaluations using CIMemories revealed that current frontier models exhibit up to a 69% rate of attribute-level violations, meaning they inappropriately leak information. While lower violation rates can be achieved, this often comes at the expense of overall task utility. The research also found that these violations accumulate over time and across multiple interactions. For instance, as usage increased from 1 to 40 tasks, violations in a model identified as GPT-5 rose from 0.1% to 9.6%. When the same prompt was executed five times, violations reached 25.1%, indicating arbitrary and unstable behavior where different attributes were leaked for identical prompts.
Attempts to mitigate these issues through "privacy-conscious prompting" were largely ineffective. Models tended to overgeneralize, either sharing all information or none, rather than making nuanced, context-dependent decisions about what information is appropriate to disclose. These findings suggest that the problem stems from fundamental limitations in the LLMs' ability to reason contextually, rather than merely requiring better prompting strategies or increased model scaling.
Further research has explored methods to instill contextual integrity in LLMs through reasoning and reinforcement learning. One approach involves explicitly prompting LLMs to reason about contextual integrity when deciding what information to disclose. This method was extended by developing a reinforcement learning (RL) framework designed to further embed the necessary reasoning into models.
Using a synthetic dataset of 700 examples featuring diverse contexts and information disclosure norms, this method demonstrated a substantial reduction in inappropriate information disclosure while maintaining task performance across various model sizes and families. Crucially, the improvements achieved on this synthetic dataset transferred to established contextual integrity benchmarks, such as PrivacyLens, which uses human annotations to evaluate privacy leakage in AI assistant actions and tool calls. This suggests that a combination of explicit reasoning and reinforcement learning could be a viable path toward addressing the contextual integrity challenges in LLMs.

JetBrains is urging Cadence users to revoke and rotate all credentials following a security incident last month in which unidentified threat actors exploited a recently disclosed critical vulnerability in TeamCity to breach its own environment. "Cadence users should immediately revoke or rotate all credentials and secrets that may have been used to run their Cadence executions," JetBrains said.
A weakness has been identified in Tenda CP3 27.5.57.101. This issue affects some unknown processing of the file Net/NetCheckPing.cpp. This manipulation of the argument interface_name/host causes os command injection. The attack can be initiated remotely.
A security flaw has been discovered in Tenda CP3 27.5.57.101. This vulnerability affects the function SystemAsh of the file Apis/system.c of the component Kylin. The manipulation of the argument AlarmVoiceURL results in os command injection. It is possible to launch the attack remotely.

OpenAI has announced a $1 billion commitment to provide subsidized access to its Daybreak AI cybersecurity tools for under-resourced critical infrastructure defenders. The initiative, named Daybreak for Frontline Defenders, will offer AI models, training, and technical support over the next six months, prioritizing water and wastewater utilities, electric grid operators, and local government entities. This move aims to equip organizations with limited budgets and staff against increasingly sophisticated cyber threats.

Attackers are exploiting a new unpatched vulnerability in Magento Open Source and Adobe Commerce that lets them run malicious code on an online store's server without logging in, Dutch e-commerce security company Sansec said in an advisory published on September 5. Sansec, which discovered the flaw and named it StyleSmuggler, said attacks started on September 4. "Sansec is publishing early
In BPF instructions that load/store a value from/to a scratch memory register the register index is an unsigned 32-bit integer and must not exceed 15, but libpcap BPF interpreter does not validate the value. In particular uncommon use cases a crafted filter program can cause the interpreter to try reading and writing the OS process memory in the 16GiB starting at the current stack frame on 64-bit architectures and in the entire address space on 32-bit architectures.