/

CVE-2026-72591

Severity:

HIGH RISK

(7.7)

Server-Side Request Forgery (CWE-918) in Koito Web API

CVE-2026-72591

Deferred

Vulnerability type

Category:

Server-Side Request Forgery

CWE:

CWE-918

Impact:

Unauthorized server-side network access

Severity:

HIGH RISK

(7.7)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Koito contains a server-side request forgery vulnerability in the album image update endpoint. An authenticated user may supply a crafted image URL that causes the server to send HTTP requests to arbitrary internal or external hosts.

Affected context

The vulnerability occurs in Koito deployments that expose the album image update API and accept user-controlled values for image_url. It becomes risky when the server retrieves or processes that URL without sufficiently restricting destinations, protocols, redirects, or access to private network ranges.

Exploit preconditions

  • Attack surface: The PATCH /apis/web/v1/album/{id}/image endpoint
  • Required access: An authenticated Koito user who can update an album image
  • Trigger point: Server-side retrieval of the supplied image_url
  • Why exploitation is possible: The application may trust a user-controlled URL and use the server's network position and permissions to make outbound HTTP requests

Why this happens

The underlying issue is insufficient validation and destination control for a user-supplied URL used in a server-side request. This behavior maps to CWE-918: Server-Side Request Forgery, where an application makes network requests on behalf of a user without reliably distinguishing permitted public destinations from protected internal resources.

Potential impact

  • An attacker may access services that are reachable from the Koito server but not from the public internet
  • The vulnerability could expose internal service responses or cloud instance metadata
  • The server may be used to probe internal network locations and service availability
  • Sensitive information may be disclosed if retrieved responses are returned, stored, or processed by the application
  • The affected host may be abused to send requests to external systems

General mitigation guidance

Mitigation generally focuses on reducing trust in user-controlled URLs and enforcing explicit outbound request policies.

Common defensive patterns include:

  • Allowing only approved URL schemes, such as HTTPS, and rejecting unsupported protocols
  • Restricting requests to an explicit allowlist of trusted hosts or media origins
  • Resolving hostnames and validating resulting addresses against private, loopback, link-local, and reserved ranges
  • Rechecking destinations after redirects and preventing DNS-rebinding paths
  • Applying short timeouts, response-size limits, and controlled egress networking
  • Running the application with minimal network permissions and limiting access to sensitive metadata services
  • Separating image retrieval from privileged internal services where practical

How teams detect issues like this

High-level detection approaches include:

  • Static analysis for HTTP clients that consume request parameters without destination validation
  • Code review checks for URL allowlist enforcement, redirect handling, DNS resolution, and private-address blocking
  • Runtime monitoring of outbound requests from the Koito process, especially connections to loopback, private, link-local, or metadata addresses
  • Web application firewall and API policy rules that detect anomalous image URL destinations
  • Network policies that restrict unnecessary egress from the application container or host
  • Automated security review tools that flag user-controlled URLs reaching server-side request functions

Sources

SourceLink
github.comgithub.com/gabehf/Koito

Frequently asked

questions

Yes, within the application's access model. An authenticated user may be able to trigger server-side requests through the exposed album image update endpoint.

The attacker must have valid authentication and sufficient permission to update an album image. The exact scope depends on Koito's authorization configuration.

Treat image URLs as untrusted input and permit requests only to explicitly approved schemes and destinations, with redirect, DNS, and private-network protections.

Combine strict URL validation with outbound network controls, least-privilege service permissions, egress monitoring, and code-review policies for server-side HTTP requests.

Find out what's already
exploitable in your codebase.