dbcve.org
Vnet\/ip Interface PackageApplication · Yokogawa

CVE-2025-48019

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
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
A vulnerability has been found in Vnet/IP Interface Package provided by Yokogawa Electric Corporation. If affected product receives maliciously crafted packets, Vnet/IP software stack process may be terminated. The affected products and versions are as follows: Vnet/IP Interface Package (for CENTUM VP R6 VP6C3300, CENTUM VP R7 VP7C3300) R1.07.00 or earlier

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

A denial-of-service vulnerability in Yokogawa Vnet/IP Interface Package allows remote attackers to send maliciously crafted packets that terminate the Vnet/IP software stack process, disrupting industrial control operations.

MitigationApply vendor-supplied patches when available; otherwise, implement network segmentation and firewall rules to restrict untrusted traffic to Vnet/IP interfaces.

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
Vnet\/ip Interface PackageApplication
Affected:< r1.08.00

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

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 installed Vnet/IP Interface Package version
    Locate the Vnet/IP Interface Package installation directory and check the version information file, or use the software's About/Version dialog if accessible. Common locations include C:\Program Files\Yokogawa\VnetIP or similar installation paths.
    Affected if The displayed version is earlier than r1.08.00 (for example, r1.07.00, r1.06.00, etc.)
  2. Confirm Vnet/IP service is running
    Open Windows Services or use the command 'sc query VnetIP' (or the relevant service name) to verify the Vnet/IP software stack process is active.
    Affected if The Vnet/IP service is running and exposed to network traffic.
  3. Check network accessibility of Vnet/IP interfaces
    Use 'netstat -an | findstr <port>' to identify listening ports associated with Vnet/IP, or review firewall rules to determine if the interface accepts external connections on industrial control ports.
    Affected if Vnet/IP interfaces are listening on accessible network ports and accept packets from untrusted sources.

You are affected if the installed Vnet/IP Interface Package version is r1.07.00 or earlier (before r1.08.00) and the Vnet/IP service is running with network-accessible interfaces.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches when available; otherwise, implement network segmentation and firewall rules to restrict untrusted traffic to Vnet/IP interfaces.

Recommended fix Moderate confidence

Vnet/IP Interface Package r1.08.00

  1. Identify the currently installed Vnet/IP Interface Package version on the affected system (CENTUM VP R6 VP6C3300 or CENTUM VP R7 VP7C3300)
  2. Obtain the fixed version r1.08.00 from official Yokogawa Electric Corporation sources (web-material3.yokogawa.com)
  3. Review the Yokogawa upgrade documentation and release notes for Vnet/IP Interface Package r1.08.00
  4. Execute the vendor-approved upgrade procedure to install r1.08.00, following all pre-installation requirements such as backing up current configuration
  5. After completing the upgrade, verify the Vnet/IP service is running normally and confirm the software stack process is stable
  6. As an additional mitigation before upgrade is possible, configure firewall rules or network segmentation to restrict untrusted packets from reaching the Vnet/IP interface

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Vnet\/ip Interface Package Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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