CVE-2026-10763
Received Received - Intake

Insecure HTTP Communication in PROMOD V via Digipede Server

Vulnerability report for CVE-2026-10763, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-06-30

Last updated on: 2026-06-30

Assigner: Hitachi Energy

Description

PROMOD V is using insecure HTTP communication instead of HTTPS. The vulnerability is due to the lack of HTTPS support from 3rd party Digipede server.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-06-30
Last Modified
2026-06-30
Generated
2026-06-30
AI Q&A
2026-06-30
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Currently, no data is known.

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Impact Analysis

Using insecure HTTP communication can expose data transmitted between PROMOD V and the Digipede server to interception or tampering by attackers.

This can lead to potential data breaches, loss of confidentiality, and integrity of the information exchanged.

Executive Summary

This vulnerability involves PROMOD V using insecure HTTP communication instead of the secure HTTPS protocol.

The root cause is that the 3rd party Digipede server does not support HTTPS, which forces PROMOD V to communicate over HTTP.

Detection Guidance

This vulnerability involves PROMOD V using insecure HTTP communication instead of HTTPS due to lack of HTTPS support from a 3rd party Digipede server.

To detect this vulnerability on your network or system, you can monitor network traffic for HTTP connections to the Digipede server instead of HTTPS.

  • Use network traffic analysis tools like Wireshark or tcpdump to capture traffic and filter for HTTP (port 80) connections to the Digipede server.
  • Example tcpdump command: tcpdump -i <interface> host <Digipede_server_IP> and port 80
  • Check application logs or configuration to verify if HTTPS is being used or if only HTTP communication is established.
Mitigation Strategies

Since the vulnerability is caused by the lack of HTTPS support from the 3rd party Digipede server, immediate mitigation steps include:

  • Avoid transmitting sensitive data over the insecure HTTP connection.
  • Restrict network access to the Digipede server to trusted hosts only.
  • Contact the vendor or 3rd party provider to request HTTPS support or a secure communication method.
  • Implement network-level encryption such as VPN tunnels to protect data in transit if HTTPS cannot be immediately enabled.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-10763. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart