UBUNTU-CVE-2026-56712: High severity ubuntu/cog vulnerability

Published Nov 10, 2026

Updated

Replicate Cog through 0.23.1 contains a server-side request forgery vulnerability that allows attackers to cause the Cog process to make server-side HTTP requests by submitting prediction inputs with attacker-controlled URLs that are not validated against the resolved destination host or IP before fetching. Attackers can supply malicious URLs or exploit HTTP redirects in cog.File and cog.Path predictor inputs to force requests to internal addresses, potentially exposing sensitive internal services or credentials.

Affected Software

2 affected components

ubuntu/cog*

Event History

Nov 10, 2026

CVE Published

via OSV·12:00 AM

Data Sourced

via OSV·12:00 AM

DescriptionSeverityAffected Software

Frequently Asked Questions

Who can exploit this issue?

An attacker needs the ability to submit prediction inputs to a Cog process using cog.File or cog.Path fields. No user interaction is required, and the vulnerability can be triggered remotely where the prediction interface is reachable.

Are redirects relevant to exploitation?

Yes. An attacker can provide a malicious URL directly or use HTTP redirects to reach an internal destination. The destination host or IP is not validated after URL resolution before Cog fetches it.

What resources may be exposed?

The affected Cog process can be induced to make HTTP requests to internal addresses. This may expose sensitive internal services or credentials available from the environment reachable by that process.

How can exposure be reduced if an update cannot be applied immediately?

Restrict who can submit prediction inputs containing cog.File or cog.Path values, and limit the Cog process's network access to internal services and sensitive metadata or credential endpoints. These measures reduce the ability to use attacker-controlled URLs to reach internal destinations.

UBUNTU-CVE-2026-56712: High severity ubuntu/cog vulnerability

Affected Software

Event History

Frequently Asked Questions

Who can exploit this issue?

Are redirects relevant to exploitation?

What resources may be exposed?

How can exposure be reduced if an update cannot be applied immediately?

Company

Resources

Contact

Frequently Asked Questions

Who can exploit this issue?

Are redirects relevant to exploitation?

What resources may be exposed?

How can exposure be reduced if an update cannot be applied immediately?