dbcve.org
Vnet\/ip Interface PackageApplication · Yokogawa

CVE-2025-48022

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 vulnerability in Yokogawa Vnet/IP Interface Package allows remote attackers to crash the Vnet/IP software stack process by sending specially crafted malicious packets, resulting in denial of service. The vulnerability affects CENTUM VP R6 and R7 versions up to R1.07.00.

MitigationApply vendor-provided patch/更新 to Vnet/IP Interface Package R1.07.01 or later. Additionally, implement network segmentation and firewall controls to restrict unauthorized packet traffic to affected systems.

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. Verify Vnet/IP Interface Package installation
    Locate and confirm the presence of Yokogawa Vnet/IP Interface Package software on the target system using system inventory or installed software lists
    Affected if Vnet/IP Interface Package is not found on the system, the user is not affected by this vulnerability
  2. Determine installed Vnet/IP Interface Package version
    Access the software's version information through its program properties, About dialog, or version file located in the installation directory
    Affected if Unable to retrieve version information prevents assessment but does not confirm safety
  3. Compare version against affected range
    Compare the identified version number to the affected range: any version prior to r1.08.00 including all R6 and R7 versions up to R1.07.00
    Affected if Installed version is r1.07.00 or earlier, or any version number less than r1.08.00, indicating the system is vulnerable
  4. Assess network exposure
    Determine if the affected system with Vnet/IP Interface Package is accessible from untrusted networks, as the vulnerability is exploitable via malicious network packets
    Affected if System is directly accessible from external or untrusted networks without firewall segmentation increases exploitation risk

User is affected if Yokogawa Vnet/IP Interface Package is installed with any version prior to r1.08.00, particularly on CENTUM VP R6 or R7 systems exposed to network 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.

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

Apply vendor-provided patch/更新 to Vnet/IP Interface Package R1.07.01 or later. Additionally, implement network segmentation and firewall controls to restrict unauthorized packet traffic to affected systems.

Recommended fix High confidence

r1.08.00

  1. Identify the current version of Vnet/IP Interface Package installed on the system
  2. Download Vnet/IP Interface Package version r1.08.00 or later from the vendor's official source (web-material3.yokogawa.com)
  3. Follow Yokogawa's documented upgrade procedure to install the new version
  4. Verify the installed version is r1.08.00 or later after the upgrade

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-48022 — 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-48022 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