CVE-2026-114493 LocalAI CVE debrief

Who should care

Defenders responsible for LocalAI deployments should assess exposure and prioritize verification and remediation efforts. This includes reviewing and updating gallery config URLs, monitoring for suspicious activity, and verifying affected deployments to prevent potential SSRF bypass. Additionally, defenders should consider the potential operational impacts of this vulnerability, including the exposure of internal or cloud metadata addresses.

Why it matters

LocalAI v4.6.0 through v4.11.0 SSRF Guard Bypass via HTTP Redirects allows attackers to submit a config URL through POST /models/apply that redirects to internal or cloud metadata addresses, receiving those internal responses as gallery content.

• Defenders must verify affected LocalAI deployments to prevent SSRF bypass
• Internal or cloud metadata addresses may be exposed to attackers
• Suspicious activity related to internal or cloud metadata addresses should be monitored

Technical summary

LocalAI v4.6.0 through v4.11.0 contains a server-side request forgery vulnerability in core/gallery/gallery.go that validates only the initial gallery config URL. Attackers can submit a config URL through POST /models/apply that redirects to internal or cloud metadata addresses, receiving those internal responses as gallery content. The vulnerability is caused by incomplete validation of the gallery config URL, allowing attackers to bypass the SSRF guard and potentially access sensitive internal or cloud metadata. Defenders should prioritize verifying affected LocalAI deployments and assessing exposure to internal or cloud metadata addresses.

Defensive priority

Defenders should prioritize verifying affected LocalAI deployments and assessing exposure to internal or cloud metadata addresses.

Recommended defensive actions

• Verify affected LocalAI deployments and assess exposure to internal or cloud metadata addresses
• Review and update gallery config URLs to prevent SSRF bypass
• Monitor for suspicious activity related to internal or cloud metadata addresses
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and source item provide details on the vulnerability, including affected versions and technical descriptions. The vulnerability is caused by the incomplete validation of the gallery config URL, which allows attackers to bypass the SSRF guard. The source item and CVE record do not provide explicit evidence of exploitation, but defenders should verify affected deployments to prevent potential SSRF bypass. The CVE Program record and NVD detail page offer additional context on the vulnerability and its potential impact.

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.