CVE
Barox Kommunikation RY-GSP22-26/370 credential disclosure in API
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- Fixed in RY-GSP22-26/370 1.03.1740 · RY-LGSP23-10G 6.54.3960
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Firmware older than 6.54.3960 on RY-LGSP23-10G, or older than 1.03.1740 on RY-GSP22-26/370. Attacker must be an authenticated user with administrative privileges.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 16/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The sensitive information disclosure flaw affects barox Kommunikation GmbH RY-GSP22-26/370 and barox Kommunikation AG RY-LGSP23-10G. A remote attacker who already has administrator access can use the API to dump the credentials of all accounts stored on the device, which could then be reused for lateral movement or further compromise.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Original description
The vulnerability enables any attacker with admin access to dump credentials of all accounts stored on the device, which can then be reused for lateral movement or further compromise. Since passwords are stored or processed in a recoverable format, this represents a critical failure in secure credential handling.
Who should check
Operators of barox RY-LGSP23-10G or RY-GSP22-26/370 switches running firmware below 6.54.3960 or 1.03.1740 respectively.
“Update to the firmware version 6.54.3960 for RY-LGSP23-10G or 1.03.1740 for RY-GSP22-26/370.”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.2/10CVSS 8.2
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Firmware older than 6.54.3960 on RY-LGSP23-10G, or older than 1.03.1740 on RY-GSP22-26/370. Attacker must be an authenticated user with administrative privileges.Upgrade to a fixed version: RY-GSP22-26/370 1.03.1740 · RY-LGSP23-10G 6.54.3960.
Workaround: Grant administrative rights only to trusted users and restrict management interface access to authorized management systems until the update is applied.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129690 (Sensitive information disclosure via API), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129690 (entry last updated 2026-11-16):
Affected:
- barox Kommunikation GmbH RY-GSP22-26/370: fixed in 1.03.1740
- barox Kommunikation AG RY-LGSP23-10G: fixed in 6.54.3960
Fixed versions: 1.03.1740, 6.54.3960.
Conditions (all must be true for the bug to be hit):
- Firmware older than 6.54.3960 on RY-LGSP23-10G, or older than 1.03.1740 on RY-GSP22-26/370. (source: https://www.cve.org/CVERecord?id=CVE-2026-129690)
- Attacker must be an authenticated user with administrative privileges. (source: https://security.barox.ch/advisories/detail?nr=BSEC-ADV-2026-0001)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
Workaround: Grant administrative rights only to trusted users and restrict management interface access to authorized management systems until the update is applied. (source: https://www.cve.org/CVERecord?id=CVE-2026-129690)
CISA KEV: CVE-2026-129690 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129690 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://security.barox.ch/advisories/detail?nr=BSEC-ADV-2026-0001
- https://www.cirosec.de/sa/sa-2026-010
- https://www.cve.org/CVERecord?id=CVE-2026-129690
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129690
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129690"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- barox Kommunikation GmbH RY-GSP22-26/370
fixed in 1.03.1740
- barox Kommunikation AG RY-LGSP23-10G
fixed in 6.54.3960
Evidence 4
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129690
Is CVE-2026-129690 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An authenticated user with administrative privileges can retrieve the passwords of other local users in plaintext through the management API. The impact is limited to administrators reading other local users' credentials.Source: cve.org, security.barox.ch
Which versions are affected by CVE-2026-129690?
RY-GSP22-26/370: before 1.03.1740. RY-LGSP23-10G: before 6.54.3960.Source: cve.now feed data
Am I affected, and how do I check?
Firmware older than 6.54.3960 on RY-LGSP23-10G, or older than 1.03.1740 on RY-GSP22-26/370, is affected. Check the firmware version on the device to compare it with these versions.Source: cve.org, security.barox.ch
How do I fix CVE-2026-129690?
Update RY-LGSP23-10G to firmware 6.54.3960 or RY-GSP22-26/370 to firmware 1.03.1740. Until the update is applied, grant administrative rights only to trusted users and restrict management interface access to authorized management systems.Source: cve.org, security.barox.ch