dbcve.org
Fast\/toolsApplication · Yokogawa

CVE-2025-66601

MEDIUM · 6.1 CVSS v3.1 Published 2026-02-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
A vulnerability has been found in FAST/TOOLS provided by Yokogawa Electric Corporation. This product does not specify MIME types. When an attacker performs a content sniffing attack, malicious scripts could be executed. The affected products and versions are as follows: FAST/TOOLS (Packages: RVSVRN, UNSVRN, HMIWEB, FTEES, HMIMOB) R9.01 to R10.04

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 · high confidence

FAST/TOOLS web applications fail to specify MIME types in HTTP responses, allowing browsers to perform content sniffing. Attackers can exploit this to execute malicious scripts by uploading or serving files that browsers may interpret as HTML/JavaScript (e.g., uploading a file with malicious JS content that gets interpreted as text/html).

MitigationConfigure web servers and application endpoints to explicitly set proper Content-Type headers (e.g., Content-Type: text/plain for user-uploaded content) and add X-Content-Type-Options: nosniff to prevent browsers from guessing content types.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Fast\/toolsApplication
Affected:>= r9.01, <= r10.04

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
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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. Check FAST/TOOLS installed version
    Locate the FAST/TOOLS installation directory and check the version information, typically found in an About dialog, version file, or by querying the application directly. Common locations include the installation folder or the application's login page banner.
    Affected if The installed version is r9.01, r9.02, r9.03, r9.04, r9.05, r10.01, r10.02, r10.03, or r10.04 (any version from r9.01 through r10.04 inclusive).
  2. Identify web-accessible endpoints
    Review the FAST/TOOLS configuration to identify web-facing URLs, particularly file upload forms, file serving endpoints, or any URL that returns user-supplied or dynamically generated content.
    Affected if The application exposes any web-accessible endpoint that serves files or user content without enforcing Content-Type headers.
  3. Inspect HTTP responses for Content-Type header
    Use a browser developer tool or HTTP proxy (e.g., Burp Suite, Fiddler) to capture HTTP responses from FAST/TOOLS web endpoints. Specifically check responses that return file content or user-uploaded files for the presence of the Content-Type header.
    Affected if The HTTP response for file-serving or file-upload endpoints lacks a Content-Type header, or the Content-Type header value does not match the actual file type being served.
  4. Inspect HTTP responses for X-Content-Type-Options header
    In the same HTTP capture, check whether the X-Content-Type-Options header is present and set to 'nosniff' on responses that serve content.
    Affected if The X-Content-Type-Options header is missing or is not set to 'nosniff' on responses, allowing browsers to perform content-type sniffing.

The environment is affected if FAST/TOOLS version is between r9.01 and r10.04 inclusive AND web responses lack proper Content-Type headers or the X-Content-Type-Options: nosniff directive, enabling content sniffing attacks.

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

Configure web servers and application endpoints to explicitly set proper Content-Type headers (e.g., Content-Type: text/plain for user-uploaded content) and add X-Content-Type-Options: nosniff to prevent browsers from guessing content types.

Fix this in Fast\/tools Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-66601 — 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-66601 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