Skip to content

Add agent-driven SSRF replay and async authorization drift risks - #147

Open
balaakasam wants to merge 2 commits into
OWASP:developfrom
balaakasam:agentic-ssrf-and-async-mutation-risks
Open

Add agent-driven SSRF replay and async authorization drift risks#147
balaakasam wants to merge 2 commits into
OWASP:developfrom
balaakasam:agentic-ssrf-and-async-mutation-risks

Conversation

@balaakasam

Copy link
Copy Markdown

This PR introduces two emerging architectural risk patterns observed in agent-driven systems:

• Agent-driven replay & rebinding SSRF where stored URLs become exploitable over time.
• Asynchronous authorization drift where background agents mutate protected fields post-validation.

These additions extend API7 (SSRF) and API6 (unrestricted-access-to-sensitive-business-flows) with modern agentic abuse cases.

@balaakasam

Copy link
Copy Markdown
Author

Thank you for reviewing my contribution. This update documents a new architectural risk pattern observed in modern agentic
systems, where autonomous workflows unintentionally retain stale or over-privileged OAuth scopes across task boundaries, enabling SSRF-style exploitation paths that are not explicitly covered today.
I would appreciate any maintainer feedback and I’m happy to refine the content to better align with existing guidance or project standards.

@ErezYalon
ErezYalon changed the base branch from master to develop August 25, 2026 06:24
@ErezYalon ErezYalon added the pending community feedback Waiting to be reviewed by the community label Aug 25, 2026
@ErezYalon

Copy link
Copy Markdown
Member

Tagging this as pending community feedback. Same category as #145/#146 — this introduces new "Agentic System Risk" content, which needs broader discussion before merging. Keeping this open as a candidate for the next version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pending community feedback Waiting to be reviewed by the community

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants