dbcve.org
Race ConditionWeakness · CWE-362

CVE-2025-13036

CRITICAL · 9.2 CVSS v4.0 Published 2026-06-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An authentication bypass security issue exists within FactoryTalk Historian Site Edition. By continually sending requests to the login endpoint, an attacker may obtain a valid authentication token.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is an authentication bypass vulnerability in FactoryTalk Historian Site Edition where repeatedly sending requests to the login endpoint can eventually yield a valid authentication token. This indicates a fundamental flaw in the authentication logic, likely a race condition or timing vulnerability that allows attackers to circumvent normal authentication controls.

MitigationImplement proper rate limiting and account lockout mechanisms on the login endpoint, and work with the vendor to obtain a patch that fixes the underlying authentication logic flaw.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify FactoryTalk Historian installation
    Locate the FactoryTalk Historian Site Edition installation directory, typically found under C:\Program Files\Rockwell Software\FactoryTalk Historian or within the Rockwell software folder structure. Check Windows Programs and Features for 'FactoryTalk Historian Site Edition'.
    Affected if FactoryTalk Historian Site Edition is installed on the system
  2. Determine the installed version
    Open Windows Programs and Features, locate FactoryTalk Historian Site Edition, and note the version number displayed. Alternatively, check the installation directory for a version file or check the Windows registry under HKLM\SOFTWARE\Rockwell Software\FactoryTalk Historian.
    Affected if The installed version matches or falls within the affected version range for CVE-2025-13036 (check against vendor advisories for specific version numbers)
  3. Verify login endpoint accessibility
    Identify if the FactoryTalk Historian web interface or API login endpoint is accessible from the network. Check IIS configuration if web services are enabled, and determine if the login page is reachable via HTTP/HTTPS.
    Affected if The login endpoint is exposed and reachable from the network (internal or external)
  4. Check for rate limiting configuration
    Review the web server (IIS) or application configuration for rate limiting settings on the login endpoint. Look for request throttling, connection limits, or authentication attempt restrictions in web.config or IIS settings.
    Affected if No rate limiting or account lockout mechanism is configured on the login endpoint
  5. Review authentication logs for abnormal patterns
    Examine FactoryTalk Historian logs, Windows Event Logs, and IIS logs for patterns of repeated login attempts, particularly from single IP addresses or accounts that eventually succeeded. Check for authentication events that show unusual timing or volume.
    Affected if Logs show repeated login attempts that eventually succeeded, indicating potential exploitation of the timing vulnerability

A system is affected if FactoryTalk Historian Site Edition is installed, the login endpoint is network-accessible, and no rate limiting or account lockout controls are configured on the authentication mechanism.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper rate limiting and account lockout mechanisms on the login endpoint, and work with the vendor to obtain a patch that fixes the underlying authentication logic flaw.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13036 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13036 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data