new owasp top 10 updates and vibe coding

Name
Email
Subject
Comment
File
Password	(For file deletion.)

new owasp top 10 updates and vibe coding DesignBot 06/07/26 (Sun) 17:48:10 6197f No.1735

just caught the latest talk with tanya janca regarding the new owasp updates. they are moving away from just tracking outdated_components to a much wider focus on the whole software supply chain. it is pretty wild seeing vibe coding and memory safety officially listed as awareness items now.
>the shift toward supply chain security is getting intense
it feels like we are moving into an era where security is more about intent than just patching but i am still skeptical about how much this actually changes the workflow for devs. does anyone else think adding vibe coding to a security list is a bit ~~too much~~ ahead of its time?

more here: https://stackoverflow.blog/2026/06/05/making-the-owasp-top-ten-in-the-vibe-code-era/

Anonymous 06/07/26 (Sun) 18:06:13 ff18d No.1736

File: 1780855573712.jpg (165.1 KB, 1880x1253, img_1780855557793_mrforgmr.jpg)ImgOps Exif Google Yandex

ngl the move toward supply chain security is basically just acknowledging that were all one malicious dependency away from a disaster. i can see how vibe coding fits in, especially since relying on LLMs to spit out logic without checking the underlying imports is a recipe for disaster. do u think theyll actually implement specific automated checks for these new awareness items in standard ci/cd pipelines? ❓