Veracode CISO Sohail Iqbal breaks down the top security risks of AI coding agents and agentic AI, and what security teams should put in place first. If code is written at machine speed, it has to be remediated at machine speed.
| Already a Veracode customer? Log in to open a support case, track your cases, and post questions. | Log in → |
Tip: Click each tab to view Product News and Threat Intel.
Veracode CISO Sohail Iqbal breaks down the top security risks of AI coding agents and agentic AI, and what security teams should put in place first. If code is written at machine speed, it has to be remediated at machine speed.
The Top AI Coding Agent Risks And How To Mitigate Them
AI coding agents are now writing and shipping code with far less human review. Is your security keeping up?
Veracode CISO Sohail Iqbal breaks down the top security risks of AI coding agents and agentic AI, and what security teams should put in place first. If code is written at machine speed, it has to be remediated at machine speed.
What you will learn:
• Why AI agents turn your software pipeline into a black box
• How an AI agent differs from a developer using an AI assistant
• The security blind spots of vibe coding
• How hallucinated packages open the door to software supply chain attacks
• How to manage agent identity, credentials, and repository access
• Why AI can chain several low-severity vulnerabilities into one critical risk
• The first control to put in place if your developers already use AI agents daily
Chapters:
0:00 Writing code at machine speed
0:38 What changes when agents ship code
1:17 Where the risk concentrates
1:40 AI agents vs. AI coding assistants
2:45 Vibe coding and what goes unseen
3:32 Hallucinated packages and supply chain attacks
5:00 Agent identity, credentials, and access
6:32 When multiple lows become one critical
7:52 The first thing to put in place
8:52 Attackers are using AI too
🔗 Learn more about the risks of AI coding here: https://www.veracode.com/resources/analyst-reports/2026-genai-code-security-report
💡 Subscribe for more insights on Application Security, AI Coding, and DevSecOps.
#AICodingAgents #ApplicationSecurity #VibeCoding
We are excited to share September updates from the product content team!
Our new lab covers the ninth OWASP LLM Top 10 category, teaching developers to identify and mitigate AI security vulnerabilities.
To learn more: Check out the release notes and Security Labs course catalog
A fresh batch of platform updates just landed across the Veracode portfolio. Here's what's shipped since August 5th — from smarter scan notifications to sharper DAST targeting and a more capable packaging runner for GitHub and GitLab integrations.
EASM: Real-Time Scan Event Notifications
Released August 5, 2026
External Attack Surface Management (EASM) now sends real-time, in-app notifications the moment a scan completes, fails, or gets cancelled. No more manually refreshing scan status — security teams get an immediate signal, keeping threat surface monitoring responsive and shrinking the gap between detection and action.
Notifications show up directly in the EASM interface, so teams can track scan outcomes without ever leaving the workflow.
DAST: Business Unit Targeting and Scan Engine Enhancements
Released August 6, 2026
Dynamic Analysis (DAST) now lets teams assign a business unit when creating a web application or API specification target — or straight from the DAST configuration page. That makes it simple to organize and filter scan targets by business unit, a real win for organizations that need to align application security reporting with internal team and ownership structures.
The DAST scan engine also got sharper, with improved detection for CAA record checks on SSL certificates for CWE-862 — applied across both Dynamic Analysis and DAST. Better detection means more accurate identification of certificate-related misconfigurations, so teams can close gaps before they're exploited.
GitHub Workflow Integration: Check Runs Bug Fix (v2.1.2)
Released August 6, 2026
A minor release of the GitHub Workflow Integration (v2.1.2) fixes a bug where GitHub APIs weren't updating and reflecting the correct check runs status. With the fix in place, check run results now display accurately in GitHub — so developers and security teams can trust the status shown right in pull requests and commit views.
Runner Image scm-packaging-5.0.0: Expanded Packaging for GitHub and GitLab
A new default runner image — scm-packaging-5.0.0 — is now available for GitHub and GitLab repository integrations, replacing scm-packaging-3.0.0
. The updated image brings a broad refresh of underlying components, expanding support for a wider range of project types and increasing overall project coverage across repo workflows.
Updated components include:
GitHub Workflow Integration (v2.1.1) also introduces a new uninstallation workflow. Administrators can now uninstall the Veracode app from GitHub organizations directly through the Veracode Platform — streamlining lifecycle management without toggling settings in GitHub itself.
GitLab gets the same scm-packaging-5.0.0 support, enhancing packaging capabilities in repo workflows and broadening the range of project types covered.
That's the full set of updates since August 5th. For a complete history of platform changes, visit the Veracode release notes.
This update adds support for scanning packaged artifacts larger than 200 MB. No changes to existing integrations are required.
https://docs.veracode.com/updates/r/c_all_static#pipeline-scan-supports-artifacts-larger-than-200-mb
Hi Veracode Community Experts,
I have a question regarding External Control of File Name or Path (CWE-73) findings reported by Veracode Static Analysis.
To mitigate path traversal, I added the following validation method:
public static boolean isWithinBaseDir(File file, String baseDir) {
try {
String canonicalFile = file.getCanonicalPath();
String canonicalBase = new File(baseDir).getCanonicalPath();
// Ensure trailing separator so "/allowed" doesn't match "/allowedExtra/file"
if (!canonicalBase.endsWith(File.separator)) {
canonicalBase += File.separator;
}
return canonicalFile.startsWith(canonicalBase);
} catch (IOException e) {
_log.error("IOException during canonical path check: " + e.getMessage());
return false;
}
}
This method resolves both the target file path and the allowed base directory to their canonical paths and verifies that the target file is located within the allowed directory.
However, after implementing this validation, Veracode Static Analysis still reports the same CWE-73 finding.
My understanding is that isWithinBaseDir() is a runtime validation. It prevents path traversal during application execution, whereas Veracode Static Analysis does not execute the application. Instead, it performs static data-flow analysis by tracing user-controlled input from the source to the sink.
Because of this, I suspect Veracode may not recognize this runtime validation as sufficient mitigation.
Could you please confirm whether my understanding is correct? Is this the reason the finding is still being reported?
If so, what is the recommended way to fix CWE-73 so that Veracode recognizes the mitigation? Are there any Veracode-recommended coding patterns, APIs, or validation techniques that the static analyzer can recognize for this category of findings?
Any guidance or best practices would be greatly appreciated.
Thank you!
Can not fix "CWE-73: External Control of File Name or Path" vulnerability in the following Python code:
```
import os
def load_json_data(json_file_path: str) -> dict:
if not json_file_path.endswith('.json'):
raise ValueError('The file should be in json format')
# Ensure the file is in the project directory to prevent external file path traversal.
abs_path = os.path.abspath(os.path.join(PROJECT_ROOT, json_file_path))
if not abs_path.startswith(PROJECT_ROOT):
raise ValueError(f'The file path is outside the project directory: {json_file_path}')
with open(abs_path, 'r') as f:
json_data = json.load(f)
return json_data
```
Can please anyone take a look and tell how to fix it?
Create a free account
Reading is open to everyone. An account unlocks the rest.
| ✓ | Open and track support cases |
| ✓ | Ask questions and reply to threads |
| ✓ | Get product announcements as they ship |
| ✓ | Submit and vote on product ideas |
Popular resources
Veracode Docs
Step-by-step product documentation
Release Notes
What shipped, and when
Getting Started Guides
Your first setup, end to end
Product Pulse Newsletter
October 2026 Releases
Spring AI and C# source scanning in Static Analysis, plus faster Fix for SCA workflows in GitHub.
Read the NewsletterLearn & Set Up
| ▸Getting Started | ✓Onboarding |
| ¶Docs ↗ | ⇄Integrations |
Stay Current
| ↻Release Notes ↗ | !Announcements |
| ★Ideaslog in to vote |
By clicking “Accept All Cookies”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts.
.png)
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.