CVE-2025-61163: Cohere North AI Cross-Domain Vulnerability

CVE-2025-61163 Overview

CVE-2025-61163 affects Cohere North AI v1.1.5. The server implements an excessively permissive cross-domain policy that fails to validate the Origin header on incoming connection requests. This design flaw allows untrusted domains to interact with the application in ways the trust model should prevent.

Because the server accepts requests from arbitrary origins, an attacker-controlled site can initiate authenticated cross-origin interactions against a victim's active North AI session. The result is a cross-domain trust boundary violation impacting confidentiality and integrity of user data handled by the platform.

Critical Impact
Missing Origin header validation on Cohere North AI v1.1.5 enables cross-origin requests from untrusted domains, exposing authenticated sessions to unauthorized cross-domain interactions.

Affected Products

Cohere North AI v1.1.5

Discovery Timeline

2026-08-26 - CVE-2025-61163 published to the National Vulnerability Database (NVD)
2026-08-26 - Last updated in NVD database

Technical Details for CVE-2025-61163

Vulnerability Analysis

Cohere North AI v1.1.5 exposes an endpoint that accepts cross-origin connections without validating the requesting origin. The server does not compare the Origin header against an allowlist of trusted domains before completing the handshake or processing the request.

An excessively permissive cross-domain policy weakens the browser's same-origin protections. When a user authenticated to North AI visits an attacker-controlled page, that page can trigger requests that reach the North AI backend in the context of the victim's session. Because origin validation is absent, the server treats the malicious request as legitimate.

The impact depends on the endpoints reachable through the trusted session. Attackers may be able to read responses that contain sensitive data, invoke authenticated actions on behalf of the user, or exfiltrate content processed by the AI workflow.

Root Cause

The root cause is missing server-side validation of the Origin header on inbound connection requests. The server accepts connections from any domain rather than restricting acceptance to a defined allowlist of trusted origins.

Attack Vector

Exploitation requires a victim with an active, authenticated Cohere North AI session to load attacker-controlled content in the same browser. The attacker page issues cross-origin requests to the North AI server, which processes them because the Origin header is not validated. No credentials need to be stolen; the browser attaches them automatically to same-site cookies or tokens.

Refer to the public technical write-up on GitHub for reproduction details and the Cohere North product overview for product context.

Detection Methods for CVE-2025-61163

Indicators of Compromise

Inbound requests to North AI endpoints where the Origin header references domains outside the organization's trusted list.
Authenticated API calls or WebSocket connections initiated shortly after a user visited an untrusted external site.
Unexpected data access patterns tied to a single user session originating from multiple referrers.

Detection Strategies

Inspect reverse proxy and application logs for the Origin and Referer headers on connections to North AI, flagging values outside the sanctioned domain list.
Correlate browser telemetry with server-side session activity to identify cross-origin requests occurring without user-initiated navigation to the application.
Deploy a Content Security Policy (CSP) report endpoint and monitor for violations tied to North AI resources.

Monitoring Recommendations

Alert on any North AI request whose Origin header is missing or not in the trusted allowlist.
Track spikes in authenticated API traffic per session as a signal of automated cross-origin abuse.
Retain full HTTP request headers for North AI traffic to support post-incident forensics.

How to Mitigate CVE-2025-61163

Immediate Actions Required

Restrict access to Cohere North AI v1.1.5 to trusted networks until a vendor fix is applied.
Instruct users to terminate North AI sessions before browsing untrusted sites and to sign out when finished.
Contact Cohere for guidance on a patched release and confirm the version deployed in your environment.

Patch Information

No vendor advisory or patched version is referenced in the available CVE data. Monitor the Cohere North product page and the public vulnerability write-up for updates on a fixed release.

Workarounds

Enforce an allowlist of trusted origins at a reverse proxy or web application firewall in front of North AI, rejecting requests whose Origin header does not match.
Require SameSite=Strict or SameSite=Lax on session cookies to reduce the impact of cross-origin requests.
Segment North AI access behind SSO with short-lived tokens to limit the window in which a cross-origin request can succeed.

bash

# Example NGINX allowlist enforcement for the Origin header
map $http_origin $origin_allowed {
    default 0;
    "https://north.example.com" 1;
    "https://app.example.com" 1;
}

server {
    listen 443 ssl;
    server_name north-proxy.example.com;

    location / {
        if ($origin_allowed = 0) {
            return 403;
        }
        proxy_pass https://north-backend.internal;
        proxy_set_header Origin $http_origin;
    }
}