CVE-2026-7161: Software Security Vulnerability Vulnerability

CRITICAL
Advisory Identifier: GHSA-q3rc-pqw4-gcr3
Share
CVSS 9.3
CWE-656
Published
Advisory Summary

CVE-2026-7161 is a CRITICAL (CVSS 9.3) security vulnerability vulnerability (CWE-656: Reliance on Security Through Obscurity) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product uses a protection mechanism whose strength depends heavily on its obscurity, such that knowledge of its algorithms or key data is sufficient to defeat the mechanism.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-7161 at a Glance

CVE Identifier CVE-2026-7161
GHSA Identifier GHSA-q3rc-pqw4-gcr3
Severity CRITICAL
CVSS v3.1 Base Score 9.3
CWE Classification CWE-656: Reliance on Security Through Obscurity
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 9.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2026-7161

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-7161, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-656: Reliance on Security Through Obscurity, where the product uses a protection mechanism whose strength depends heavily on its obscurity, such that knowledge of its algorithms or key data is sufficient to defeat the mechanism. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

An insufficient encryption vulnerability exists in the Device Authentication functionality of GeoVision GV-IP Device Utility 9.0.5. Listening to broadcast packets can lead to credentials leak. An attacker can listen to broadcast messages to trigger this vulnerability. When interacting with various Geovision devices on the network, the utility may send privileged commands; in order to do so, the username and password of the device need to be provided. In some instances the command is broadcasted over UDP and the username/password are encrypted using a cryptographic protocol that appears to be derivated from Blowfish. However the symmetric key used for the encryption is also included in the packet, and thus the security of the username/password only relies on the "obscurity" of the encryption scheme. An attacker on the same LAN can listen to the broadcast traffic once an admin user interacts with the device, and decrypt the credentials using their own implementation of the algorithm. With this password the attacker would have full control over the device configuration, allowing them to change its ip address or even reset it to factory default.

References

NVD — CVE-2026-7161 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-7161
talosintelligence.com/vulnerability_repor... WEB
https://talosintelligence.com/vulnerability_reports
Software Security Information SECURITY
https://www.geovision.com.tw/cyber_security.php
www.talosintelligence.com/vulnerability_repor... WEB
https://www.talosintelligence.com/vulnerability_reports/TALOS-2025-2322

Frequently Asked Questions

What is CVE-2026-7161?
CVE-2026-7161 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-656: Reliance on Security Through Obscurity.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-7161?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-7161?
CVE-2026-7161 has a CVSS v3.1 base score of 9.3 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:H.
What CWE is associated with CVE-2026-7161?
CVE-2026-7161 is classified under CWE-656: Reliance on Security Through Obscurity (The product uses a protection mechanism whose strength depends heavily on its obscurity, such that knowledge of its algorithms or key data is sufficient to defeat the mechanism.).
How can I check Maven dependencies for CVE-2026-7161?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-q3rc-pqw4-gcr3",
  "modified" : "2026-06-15T21:30:25Z",
  "published" : "2026-05-04T03:31:27Z",
  "aliases" : [ "CVE-2026-7161" ],
  "details" : "An insufficient encryption vulnerability exists in the Device Authentication functionality of GeoVision GV-IP Device Utility 9.0.5. Listening to broadcast packets can lead to credentials leak. An attacker can listen to broadcast messages to trigger this vulnerability.\n\n\nWhen interacting with various Geovision devices on the network, the utility may send privileged commands; in order to do so, the username and password of the device need to be provided. In some instances the command is broadcasted over UDP and the username/password are encrypted using a cryptographic protocol that appears to be derivated from Blowfish. However the symmetric key used for the encryption is also included in the packet, and thus the security of the username/password only relies on the \"obscurity\" of the encryption scheme. An attacker on the same LAN can listen to the broadcast traffic once an admin user interacts with the device, and decrypt the credentials using their own implementation of the algorithm. With this password the attacker would have full control over the device configuration, allowing them to change its ip address or even reset it to factory default.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-7161"
  }, {
    "type" : "WEB",
    "url" : "https://talosintelligence.com/vulnerability_reports"
  }, {
    "type" : "WEB",
    "url" : "https://www.geovision.com.tw/cyber_security.php"
  }, {
    "type" : "WEB",
    "url" : "https://www.talosintelligence.com/vulnerability_reports/TALOS-2025-2322"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-656" ],
    "severity" : "CRITICAL",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-05-04T01:16:04Z"
  }
}