[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fMSMVpRz09FERX-agAvlBHtpNYGeb9IouVgLnMqf0f0k":3},{"article":4,"iocs":46,"watch_terms":47,"solutions":48,"lesson":134},{"id":5,"title":6,"slug":7,"summary":8,"ai_summary":9,"brief":10,"url":11,"image_url":12,"published_at":13,"ingested_at":14,"relevance_score":15,"entities":16,"category_id":25,"category":26,"article_tags":30},"99c17e05-0179-45d0-b3c5-a147810db743","Critical x402 SDK Flaw Could Let Malicious APIs Drain AI Agents’ Token Balances","critical-x402-sdk-flaw-could-let-malicious-apis-drain-ai-agents-token-balances-435130","AI agents paying for API calls with the x402 SDKs could sign a payment for their full balance of a supported token if a malicious API asked for it, security firm V12 said on October 22. The cause was the SDKs' default client, which set no spending limit until releases on August 18 added one. The risk was limited to agents who automatically signed payments and whose apps set","Security firm V12 discovered a critical vulnerability in x402 SDKs where the default client imposed no spending limits on API payment requests, potentially allowing malicious APIs to drain an AI agent's entire token balance. The flaw affected agents that automatically signed payments without restrictions. SDK maintainers addressed the issue with spending limit controls added in August 18 releases.","x402 SDK flaw allows malicious APIs to drain AI agents' full token balances without spending limits.","https:\u002F\u002Fthehackernews.com\u002F2026\u002F10\u002Fcritical-x402-sdk-flaw-could-let.html","https:\u002F\u002Fblogger.googleusercontent.com\u002Fimg\u002Fb\u002FR29vZ2xl\u002FAVvXsEi1nl6HARmLzzb4BlklarhKxB1F2U6dwKebASj9-Ow-WI6otLzFoATEY-icF7OCAgwHqRzwNhs9jHY2S7e4ZGRHykrIzedvLxQlAyen6jQsOoY_L80gd0Lrjy3-3xzlHavaxahxsI1o13_r2MRRDwbQrtslkXfbITBGcp_736F1sPVq7dR8Rnq_JSVQP3A\u002Fs1600\u002Fai-wallet.jpg","2026-10-23T08:35:45+00:00","2026-10-23T10:00:04.69443+00:00",7,[17,20,23],{"name":18,"type":19},"V12","vendor",{"name":21,"type":22},"x402 SDK","technology",{"name":24,"type":22},"AI agents","80544778-fabb-4dcd-aa35-17492e5dcf4f",{"id":25,"icon":27,"name":28,"slug":29},null,"Vulnerabilities","vulnerabilities",[31,36,41],{"category":32},{"id":33,"icon":27,"name":34,"slug":35},"26b0b636-0e31-4db1-bffb-61bdf9f20a58","Supply Chain","supply-chain",{"category":37},{"id":38,"icon":27,"name":39,"slug":40},"839da5c1-3c34-47e2-9499-f7201640e3ac","AI Security","ai-security",{"category":42},{"id":43,"icon":27,"name":44,"slug":45},"ade75414-7914-4e23-a450-48b64546ee70","Open Source","open-source",[],[18],{"controls":49,"vendors":133},[50,79,108],{"slug":51,"name":52,"problem":53,"products":54},"secrets-management","Secrets management","API keys, tokens and passwords stop leaking from code, chat and configuration files.",[55,63,71],{"vendor_slug":56,"vendor_name":57,"vendor_logo":58,"product_slug":59,"product_name":60,"url":61,"description":62},"gitguardian","GitGuardian","\u002Fvendor-logos\u002Fgitguardian.png","gitguardian-platform","GitGuardian Secrets Detection","https:\u002F\u002Fwww.gitguardian.com\u002F","Finds and helps remediate secrets leaked in repositories, CI pipelines and chat tools.",{"vendor_slug":64,"vendor_name":65,"vendor_logo":66,"product_slug":67,"product_name":68,"url":69,"description":70},"palo-alto-networks","Palo Alto Networks","\u002Fvendor-logos\u002Fpalo-alto-networks.png","idira-secrets-management","Idira Secrets Management","https:\u002F\u002Fwww.paloaltonetworks.com\u002Fidira\u002Fmachine\u002Fsecrets-management","Secrets management for applications, scripts and pipelines, from the former CyberArk portfolio.",{"vendor_slug":72,"vendor_name":73,"vendor_logo":74,"product_slug":75,"product_name":76,"url":77,"description":78},"github","GitHub","\u002Fvendor-logos\u002Fgithub.png","advanced-security","GitHub Advanced Security","https:\u002F\u002Fgithub.com\u002Fsecurity\u002Fadvanced-security","Dependency review, code scanning and secret scanning with push protection.",{"slug":80,"name":81,"problem":82,"products":83},"vulnerability-management","Vulnerability scanning and prioritisation","You know which systems are vulnerable, and which ones to fix first.",[84,92,100],{"vendor_slug":85,"vendor_name":86,"vendor_logo":87,"product_slug":88,"product_name":89,"url":90,"description":91},"rapid7","Rapid7","\u002Fvendor-logos\u002Frapid7.png","insightvm","Rapid7 Exposure Command (InsightVM)","https:\u002F\u002Fwww.rapid7.com\u002Fproducts\u002Finsightvm\u002F","Vulnerability scanning and risk-based prioritisation; InsightVM is now part of Exposure Command, alongside attack surface and cloud risk.",{"vendor_slug":93,"vendor_name":94,"vendor_logo":95,"product_slug":96,"product_name":97,"url":98,"description":99},"qualys","Qualys","\u002Fvendor-logos\u002Fqualys.png","vmdr","Qualys VMDR","https:\u002F\u002Fwww.qualys.com\u002Fapps\u002Fvulnerability-management-detection-response\u002F","Vulnerability management, detection and response with risk-based prioritisation.",{"vendor_slug":101,"vendor_name":102,"vendor_logo":103,"product_slug":104,"product_name":105,"url":106,"description":107},"axonius","Axonius","\u002Fvendor-logos\u002Faxonius.png","axonius-exposures","Axonius Exposures","https:\u002F\u002Fwww.axonius.com\u002Fplatform\u002Fexposures","Brings findings from different scanners together with asset and business context, to show what matters most and track fixes to the end.",{"slug":40,"name":109,"problem":110,"products":111},"AI application security","Prompt injection, data leaks through AI tools and unapproved AI use get caught.",[112,120,128],{"vendor_slug":113,"vendor_name":114,"vendor_logo":115,"product_slug":116,"product_name":117,"url":118,"description":119},"hiddenlayer","HiddenLayer","\u002Fvendor-logos\u002Fhiddenlayer.png","hiddenlayer-ai-security","HiddenLayer AI Security Platform","https:\u002F\u002Fhiddenlayer.com\u002F","Model scanning, AI red teaming and runtime protection for AI applications.",{"vendor_slug":121,"vendor_name":122,"vendor_logo":123,"product_slug":124,"product_name":125,"url":126,"description":127},"boomi","Boomi","\u002Fvendor-logos\u002Fboomi.png","boomi-agentstudio","Boomi Agentstudio","https:\u002F\u002Fboomi.com\u002Fplatform\u002Fagentstudio\u002F","Agent builder whose Agent Control Tower registers and monitors Boomi agents and agents on Amazon Bedrock, Microsoft Copilot and other platforms, keeps audit logs and can switch agents off where the provider allows it.",{"vendor_slug":64,"vendor_name":65,"vendor_logo":66,"product_slug":129,"product_name":130,"url":131,"description":132},"prisma-airs","Prisma AIRS","https:\u002F\u002Fwww.paloaltonetworks.com\u002Fai-security\u002Fprisma-airs","Security for AI applications, models and agents, including runtime protection against prompt injection.",[],{"slug":135,"title":136,"body":137,"framework_refs":138,"framework_notes":146},"x402-sdk-default-settings-could-let-rogue-apis-drain-ai-agent-wallets","x402 SDK Default Settings Could Let Rogue APIs Drain AI Agent Wallets","The x402 SDK shipped with no default spending limits, meaning AI agents would automatically approve and sign any payment request made by an API they interacted with — including malicious ones. This is a classic misconfiguration-by-default problem: the secure option (spending caps) existed but was not enforced out of the box, placing the burden of safety entirely on developers who may not have known the risk. In agentic AI systems that operate autonomously and handle real financial assets, unbounded authorization is catastrophic. The incident highlights that SDK developers must ship secure defaults, not secure options, especially when financial transactions are involved.",[139,140,141,142,143,144,145],"CIS Control 7: Continuous Vulnerability Management","OWASP A06:2021 Vulnerable and Outdated Components","NIST SP 800-53 SI-2: Flaw Remediation","ISO\u002FIEC 27001:2022 A.8.8: Management of technical vulnerabilities","NIST CSF 2.0 PR.AA: Identity Management, Authentication, and Access Control","PCI DSS Requirement 6","DORA Article 9",{"DORA Article 9":147,"PCI DSS Requirement 6":148,"NIST SP 800-53 SI-2: Flaw Remediation":149,"OWASP A06:2021 Vulnerable and Outdated Components":150,"CIS Control 7: Continuous Vulnerability Management":151,"ISO\u002FIEC 27001:2022 A.8.8: Management of technical vulnerabilities":152,"NIST CSF 2.0 PR.AA: Identity Management, Authentication, and Access Control":153},"DORA Article 9 requires financial entities to implement controls protecting the integrity and availability of digital assets and automated payment systems, making uncapped AI agent spending a direct compliance gap for in-scope organizations.","Requirement 6 mandates that payment-processing software be developed and maintained securely, including patching known vulnerabilities; this applies directly to SDKs that facilitate automated financial transactions like x402.","SI-2 requires organizations to identify, report, and correct information system flaws; applying the corrected SDK release within an organizationally defined timeframe directly satisfies this control.","The x402 SDK's unpatched default configuration is precisely the scenario OWASP A06 addresses — using components with insecure defaults or known flaws that expose applications to exploitation.","The SDK vulnerability was patched on August 18; organizations with a structured vulnerability management program tracking third-party SDK advisories would have identified and applied the fix promptly rather than remaining exposed.","A.8.8 mandates timely identification and remediation of technical vulnerabilities in software components, which would have driven rapid adoption of the patched SDK version once the flaw was disclosed.","Enforcing spending limits on AI agent payment authorizations is a form of access control — PR.AA calls for limiting the access and privileges of automated processes, which would have capped the blast radius of any malicious API interaction."]