☠️
EXFILTRATING
DATA...
01010111 10110010 00101001 11000110 01101100 10011011 00010001 11100101 01000010 10101111
[ <-- BACK_TO_SEARCH ]

CVE-2026-2813

CVE-2026-2813 Open Redirect in Esri
📅 PUBLISHED: 2026-05-20 17:51 UTC 🔄 UPDATED: 2026-09-23 20:34 UTC
[ PATCH UNDER REVIEW ↓ ] Remains UNDER REVIEW until an independent source confirms the fix
[ DEFENSE PATCH ↓ ]
💣 PoC: None
👁️
Proof of Concept - Indicates if functional exploit code is publicly available, drastically increasing the risk of immediate attacks.
🎯 EPSS: 0.30%
👁️
0.30% probability
7.5× above the median CVE
Tier: ELEVATED
30-day exploitation window · FIRST.org · updated daily
VULNERABLE: version not auto-detected — verify your deployed version locally
CVSS SEVERITY SCALE
9.0–10.0 CRITICAL
7.0–8.9 HIGH
4.0–6.9 MEDIUM
0.1–3.9 LOW
0.0 NONE
4.7
THREAT LEVEL
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2026-2813 is a client-side open redirect vulnerability in Esri ArcGIS Server version 11.5. The flaw resides in the login redirection workflow, where insufficient input validation allows an authenticated attacker to craft a malicious request that redirects the user’s browser to an untrusted external site. This is a low-severity issue (CVSS 4.7) with limited confidentiality impact, requiring user interaction and authentication. No server-side compromise or cross-component impact is possible. The vulnerability is confined to the same security boundary and affects only the client-side navigation logic during authentication.

⚡ AUTOMATE YOUR CVE INTELLIGENCE

This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.

›Patch confidence — UNVERIFIED to CONFIRMED, cross-referenced NVD + RHSA + Debian
›Exploit & PoC — poc_status, poc_url, has_exploit. Not in NVD.
›Shodan dorks — ready-made queries to find exposed vulnerable systems
›Detection rules — YARA · Wazuh · Elastic (all plans) · Sigma (Pro)
›pending_fields — know exactly which of 7 fields NVD hasn't processed yet
›Free backfill — data incomplete when you paid? Re-check within 30 days = 0 credits
PAYG €0.08/lookup Standard €19/mo (was €29) · 5k credits Pro €65/mo (was €99) · 20k credits FOUNDING PRICE · LOCKED FOR LIFE · ENDS 31 DEC 2026
[ FROM €19/MO ]
Free sandbox key available
No signup required

Supply Chain & Package Security

This vulnerability is not related to an open-source package (NPM, PyPI, Go, Ruby). It affects a proprietary enterprise GIS server product from Esri. No supply chain or package security implications are present.

CVSS Breakdown & Threat Level

  • CVSS Score: 4.7 (Medium)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: Low (Authenticated)
  • User Interaction: Required
  • Scope: Unchanged
  • Confidentiality Impact: Low
  • Integrity Impact: None
  • Availability Impact: None

Threat Level: Low. Exploitation requires authentication and user interaction, and the impact is limited to a client-side redirect with no server compromise.

Deep Dive & Mechanics

The vulnerability exists in the login redirection workflow of ArcGIS Server. When a user authenticates, the server may redirect the browser to a URL specified in a parameter (e.g., redirect or returnUrl). Due to insufficient input validation, an authenticated attacker can craft a specially crafted request that includes a malicious external URL. If a victim user clicks on the crafted link or is tricked into interacting with it, the browser will be redirected to the attacker-controlled site.

Key Technical Details:

  • The flaw is in the client-side navigation logic, not server-side processing.
  • The attacker must be authenticated to the ArcGIS Server instance.
  • The redirect occurs only during the authentication flow.
  • No server-side data is exposed or compromised.
  • The vulnerability is limited to the same security boundary (no cross-component impact).

Attack Flow:

  1. Attacker authenticates to ArcGIS Server.
  2. Attacker crafts a URL with a malicious redirect parameter (e.g., https://victim-arcgis-server.com/login?redirect=https://evil.com).
  3. Attacker sends the crafted URL to a victim (e.g., via phishing email).
  4. Victim clicks the link and is redirected to the attacker’s site after authentication.
  5. The attacker can then perform phishing or other social engineering attacks.

Vulnerable vs. Patched Code

Vulnerable Code (Conceptual): The vulnerable code likely accepts a redirect parameter without proper validation:

// Vulnerable: No validation of redirect URL
function handleLoginRedirect(redirectUrl) {
    window.location.href = redirectUrl;
}

Patched Code (Conceptual): The patched code should validate the redirect URL against a whitelist of allowed domains:

// Patched: Validate redirect URL against allowed domains
const allowedDomains = ['example.com', 'arcgis-server.com'];
function handleLoginRedirect(redirectUrl) {
    try {
        const url = new URL(redirectUrl);
        if (allowedDomains.includes(url.hostname)) {
            window.location.href = redirectUrl;
        } else {
            // Redirect to default page
            window.location.href = '/default';
        }
    } catch (e) {
        // Invalid URL, redirect to default
        window.location.href = '/default';
    }
}

Exploitation & Lab Setup

Red Team (Exploitation)

Prerequisites:

  • Access to an ArcGIS Server 11.5 instance with valid credentials.
  • A victim user who will click the crafted link.

Exploitation Steps:

  1. Identify the login endpoint (e.g., https://target-arcgis-server.com/login).
  2. Craft a malicious URL with a redirect parameter pointing to an attacker-controlled site:
    https://target-arcgis-server.com/login?redirect=https://attacker.com/phishing
    
  3. Send the crafted URL to the victim via email or other means.
  4. When the victim clicks the link and authenticates, they will be redirected to the attacker’s site.

No exploit code is available from Exploit-DB or other sources.

Blue Team (Detection & Mitigation)

Detection:

  • Monitor for unusual login redirect parameters in web logs.
  • Look for requests to /login with redirect parameters pointing to external domains.
  • Use web application firewalls (WAF) to block redirects to untrusted domains.

Mitigation:

  • Apply the vendor patch when available.
  • Implement strict input validation on the redirect parameter.
  • Use a whitelist of allowed redirect destinations.
  • Educate users about phishing attacks that exploit open redirects.

Indicators of Compromise (IOCs)

  • Network IOCs:
    • HTTP requests to /login with redirect parameter containing external domains.
    • Unusual referrer headers pointing to external sites after authentication.
  • Log IOCs:
    • Web server logs showing redirect parameter with non-standard URLs.
    • Authentication logs with unusual redirect patterns.
  • File IOCs:
    • No specific file-based IOCs.

Detection Engineering

YARA Rule

rule CVE_2026_2813_ArcGIS_Open_Redirect {
    meta:
        description = "Detects potential exploitation of CVE-2026-2813 in ArcGIS Server logs"
        author = "Valters IT"
        date = "2026-01-01"
        reference = "CVE-2026-2813"
    strings:
        $redirect_param = /redirect=https?:\/\/[^\/]+\.[^\/]+/ nocase
        $login_path = "/login" nocase
    condition:
        $login_path and $redirect_param
}

Sigma Rule

title: ArcGIS Server Open Redirect Exploitation
id: 8a9b7c6d-5e4f-3a2b-1c0d-9e8f7a6b5c4d
status: experimental
description: Detects attempts to exploit CVE-2026-2813 open redirect in ArcGIS Server
author: Valters IT
date: 2026-01-01
logsource:
    category: webserver
    product: apache
    service: http
detection:
    selection:
        cs-uri-query|contains: "/login?redirect=http"
    condition: selection
falsepositives:
    - Legitimate redirects to internal domains
level: medium

Suricata Rule

alert http any any -> any any (msg:"CVE-2026-2813 ArcGIS Server Open Redirect Attempt"; flow:to_server; content:"/login"; http_uri; content:"redirect"; http_uri; pcre:"/redirect=https?:\/\/[^\/]+\.[^\/]+/Ui"; classtype:attempted-recon; sid:1000001; rev:1;)

Remediation & Mitigation

Immediate Actions:

  1. Upgrade ArcGIS Server to a patched version when available (currently no patch).
  2. Implement input validation on the redirect parameter to only allow internal domains.
  3. Use a web application firewall (WAF) to block redirects to external domains.
  4. Monitor logs for suspicious redirect patterns.

Long-term Recommendations:

  • Apply vendor patches as soon as they are released.
  • Conduct regular security assessments of ArcGIS Server configurations.
  • Educate users about phishing attacks that exploit open redirects.
  • Implement strict URL validation for all redirect parameters.

Workarounds:

  • Disable the redirect functionality if not needed.
  • Use a reverse proxy to filter out malicious redirect parameters.

Valters IT

◈ SOURCE Analysis & enrichment: valtersit.com/cve/CVE-2026-2813/ · CVE data: NVD/MITRE (public domain) · © 2026 ValtersIT Hub
>_ SYSTEM_CORE: INTEL_ACTIVE
90% TEAM-CURATED // 10% AUTOMATED INGESTION.
ALL PATCH REFERENCES AND VERSION DATA SOURCED FROM NVD + OSV OFFICIAL REGISTRIES.