CVE-2026-108115 Kortix AI CVE debrief

Who should care

Defenders responsible for Kortix Suna deployments, especially those with untrusted project managers, should assess exposure and prioritize verification of instance configuration and network reach.

Why it matters

Defenders should care about CVE-2026-108115 because it allows project managers to potentially access internal services and cloud metadata endpoints, risking sensitive information disclosure. Verification of Kortix Suna instance configuration and network reach is necessary to assess exposure.

• Potential unauthorized access to internal services
• Possible exposure of cloud metadata endpoints
• Risk of sensitive information disclosure
• Need for verification of instance configuration and network reach

Technical summary

The Kortix Suna server-side request forgery vulnerability allows project managers to bypass the isPrivateIp guard by supplying IPv6 6to4 or Teredo addresses that embed private IPv4 destinations. This could potentially allow them to reach internal services and cloud metadata endpoints. The vulnerability exists in Kortix Suna versions 0.10.7 before 0.13.52. Users holding project.connector.write permission can set connector base_url, OpenAPI, Postman, or MCP URLs to access these internal services and read responses. Defenders should prioritize verifying exposure of Kortix Suna instances to untrusted project managers and assessing the network reach of internal services and cloud metadata endpoints.

Defensive priority

Defenders should prioritize verifying exposure of Kortix Suna instances to untrusted project managers and assessing the network reach of internal services and cloud metadata endpoints.

Recommended defensive actions

• Verify Kortix Suna instance exposure to untrusted project managers
• Assess network reach of internal services and cloud metadata endpoints
• Restrict project.connector.write permission to trusted users
• Monitor for suspicious connector URL changes
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD entry provide details on the vulnerability. Further verification is needed to assess the scope of affected deployments and potential impact. Defenders should verify Kortix Suna instance configuration, network reach, and exposure to untrusted project managers. Evidence limits and potential blind spots in source information should be considered.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.