CuraSec

tag: Agentic-Security · 3 items

  • Engineer — Plan: Confirmed post-approval state-substitution in Agno AgentOS ≤3.0.9 and LangGraph Agent Server ≤0.14.0 — if you ship AI agent workflows with human-in-the-loop gates, audit these dependencies and upgrade to patched releases; review approval-to-execution binding in any custom agent code.
  • SOC/IR — Learn: Novel attack class showing that human approval gates in agentic systems can be bypassed via state mutation or misrepresentation; no IOCs or ATT&CK-mapped TTPs to hunt for today, but worth understanding as AI agent deployments expand detection scope.
  • Leader — Plan: If your organization is deploying AI agents with human-approval checkpoints, this research establishes that approval binding is an unsolved control problem in major frameworks — use it to drive a policy review of agentic AI deployments and require vendors to document their approval-integrity guarantees this quarter.
2026-09-17 · The Hacker News · source ↗ #agentic-security#pentesting#ai
  • Engineer — Skip
  • SOC/IR — Skip
  • Leader — Learn: The patch-gap statistics (5-day exploit vs. 43-day median patch) are independently corroborated by Mandiant and Verizon DBIR 2026, making this useful benchmarking data for board-level risk conversations about continuous testing investment.
  • Engineer — Learn: Reinforces that client-side-only enforcement is exploitable by AI agents, not just human attackers; audit APIs accessible to AI agents for missing server-side authorization controls.
  • SOC/IR — Learn: No IOCs, ATT&CK mappings, or detection surface provided; useful context for understanding how agentic AI can abuse application-logic flaws, but yields no immediate hunt or rule-writing work.
  • Leader — Plan: If your organization deploys or evaluates AI agents with API access, establish explicit scope and permission guardrails this quarter — this incident shows agents can cause measurable harm to third parties, creating liability and customer-trust risk.