CuraSec

tag: Memory-Poisoning · 2 items

  • Engineer — Learn: Research demonstrates that multimodal agent memory pipelines can be poisoned or injected via imperceptible image perturbations with ~60% success rates; no patch exists yet, but teams building RAG or memory-backed AI agents should design for untrusted visual input and avoid unconditional trust in retrieved visual context.
  • SOC/IR — Learn: Novel attack class against AI agent memory systems; no IOCs or exploited-in-the-wild evidence, but detection engineers supporting AI-enabled products should be aware this failure mode exists for future coverage planning.
  • Leader — Skip
  • Engineer — Learn: Novel prompt-injection variant that abuses persistent agent memory via a malicious email payload; no patch or KEV exists, but engineers building AI agents with memory + inbox access should audit whether memory writes can be triggered by untrusted input and add confirmation gates before persisting new user ‘facts’.
  • SOC/IR — Learn: No IOCs, ATT&CK mappings, or active exploitation reported; the attack’s stealthiness makes detection at the SIEM/EDR layer impractical without application-layer logging of memory writes, so this is awareness context for future detection design rather than an actionable hunt.
  • Leader — Plan: Organizations piloting AI assistants with memory and email access now have a concrete manipulation risk to include in AI deployment governance — draft or update your AI agent policy this quarter to require human approval before agents persist new user-context facts sourced from inbound messages.