Vulnerability in RUGGEDCOM RST2428P (6GK6242-6PA00) (CVE-2026-41918)
Summary
Vulnerability in RUGGEDCOM RST2428P (6GK6242-6PA00) (CVE-2026-41918). Confidential information can be exposed externally.
Original description
The description as published by the source.
A vulnerability has been identified in RUGGEDCOM RST2428P (6GK6242-6PA00) (All versions < V4.0). The affected applications stores sensitive information in the browser cache when an authenticated user modify specific configurations. This could allow an authenticated attacker to access sensitive data stored in the browser.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-41918 has been found in RUGGEDCOM RST2428P (6GK6242-6PA00).
Confidential information can be exposed externally. CVSS score: 5.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "RUGGEDCOM RST2428P (6GK6242-6PA00) CVE-2026-41918" on the vendor's site.
CVE-2026-41918 (RUGGEDCOM RST2428P (6GK6242-6PA00)) — CWE-525 / CVSS v3 5.7
Attack vector: remote (network-reachable)
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-525) exists in RUGGEDCOM RST2428P (6GK6242-6PA00).
Check the vendor advisory for the affected versions of RUGGEDCOM RST2428P (6GK6242-6PA00).
Severity: Medium (CVSS 5.7/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで RUGGEDCOM RST2428P (6GK6242-6PA00) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web productcert@siemens.com
- web nvd.nist.gov
- web github.com