Security Advisory

CVE-2023-32348: Teltonika RMS VPN Hub SSRF

Last updated:
  • CVE-2023-32348

CVE-2023-32348 is a routing flaw in the VPN hub of Teltonika's Remote Management System (RMS) before 4.10.0: the OpenVPN server behind the hub let a connected client reach every Teltonika device on the VPN and route connections onward, so an attacker could scan and access data from other customers' devices. NVD and CISA score it 5.8.

Vulnerability summary

CVSS base score

5.8

Medium severity

EPSS score (FIRST)

0.5%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2023-32348 · Source: NVD

Affected components

ComponentCPEVersion range
Teltonika Remote Management System (RMS) cloud platformcpe:2.3:a:teltonika:remote_management_system:*:*:*:*:*:*:*:*Before 4.10.0 (NVD, CVE record, CISA ICSA-23-131-08); fixed server-side by Teltonika
Teltonika routers managed through RMS—No router firmware range is given for this CVE; Teltonika recommends the latest firmware (CISA ICSA-23-131-08)

What does this mean for affected devices?

CISA, the CNA, describes it: "Teltonika's Remote Management System versions prior to 4.10.0 contain a virtual private network (VPN) hub feature for cross-device communication that uses OpenVPN. It connects new devices in a manner that allows the new device to communicate with all Teltonika devices connected to the VPN. The OpenVPN server also allows users to route through it. An attacker could route a connection to a remote server through the OpenVPN server, enabling them to scan and access data from other Teltonika devices connected to the VPN." CISA classes it CWE-918, server-side request forgery; NVD lists only the CNA's CWE. The record was published on 2023-05-22 (NVD, CVE record). It is one of eight CVEs in CISA's ICSA-23-131-08, published on 2023-05-11, which credits Roni Gavrilov of OTORIO and Noam Moshe of Claroty Research. Their joint findings are written up by Claroty Team82.

How does the attack work?

The RMS Device VPN Hub builds a private network over Teltonika's infrastructure between routers and remote devices. When a router joins a hub, RMS downloads an OpenVPN configuration with private keys and certificates to it and starts an OpenVPN client. Claroty Team82 found that Teltonika's OpenVPN server would route traffic onward, so a connected client could reach anything the server itself could reach. The researchers say they accessed AWS infrastructure, exfiltrated identification tokens and reached internal Teltonika services this way. CISA's summary focuses on the device side: an attacker could scan and access data from other Teltonika devices on the VPN.

How severe is it?

NVD's Primary score and CISA's score agree: CVSS v3.1 5.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N). The changed scope reflects that the flaw in the VPN server exposes other systems, the routers and services behind it. CISA's CSAF file carries the same values as CVSS v3.0. For a router owner, the practical point is that a shared cloud VPN put their device on a network with other customers' devices.

How was it fixed, and what should owners do?

RMS is Teltonika's cloud service, so the fix was made on Teltonika's side: CISA says the RMS services "have already been updated to versions, which fix these vulnerabilities", and Teltonika recommends that users update their devices to the latest versions. There is nothing to install on the RMS side. Teltonika's RUT241 Cloud Solutions page describes RMS as its cloud system for remote monitoring and management of Teltonika devices; the RMS connection type defaults to Enabled, and on routers that are not managed from RMS setting it to Disabled stops all connection attempts, which takes the device out of the cloud path described in this advisory. Where a VPN hub is still used, treat it as an untrusted network and keep the router's management services and local LAN filtered from the VPN interface.

The Teltonika router vulnerability guide covers RMS features and RutOS firewall zones. The same advisory covers CVE-2023-32346, enumeration of registered routers, CVE-2023-2588, unauthenticated RMS proxy URLs, and the router firmware flaw CVE-2023-32350.

CVE-2023-32348 is not in the CISA KEV catalog as of 2026-11-21 (catalog version 2026.11.20, 1,790 entries). FIRST EPSS gives it 0.00526, the 45.5th percentile, in the 2026-11-20 dataset (CISA KEV, FIRST EPSS).

How to fix this class of issueNo dedicated SoftWSP guide covers this weakness class; the fix is usually the vendor patch or firmware update referenced above. Our related guide explains how to plan and verify it: NIST SP 800-40 Rev. 4: enterprise patch management planning, explained.

Evidence

  • NVD (read 2026-11-21): status Modified; published 2023-05-22; source [email protected]; NVD Primary CVSS v3.1 5.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N; CISA ICS Secondary 5.8 same vector; CWE CWE-918 (CNA only); CPE Teltonika Remote Management System before 4.10.0; reference ICSA-23-131-08. — NVD
  • CISA ICSA-23-131-08 CSAF (2023-05-11), read 2026-11-21: Teltonika Remote Management System and RUT Model Routers; credits Roni Gavrilov (OTORIO) and Noam Moshe (Claroty Research); RMS services already updated to versions that fix these vulnerabilities; Teltonika recommends updating devices to the latest versions; no known public exploitation reported to CISA; sectors Water and Wastewater, Energy, Critical Manufacturing. CVE-2023-32348: CWE-918, CVSS v3.0 5.8 AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N; the RMS VPN hub uses OpenVPN, connects new devices so they can communicate with all Teltonika devices on the VPN, and the OpenVPN server allows routing through it, enabling scanning and data access on other Teltonika devices. — CISA CSAF ICSA-23-131-08
  • Claroty Team82 'Triple Threat: Breaking Teltonika Routers Three Ways', read 2026-11-21: CVE-2023-32348: Device VPN Hub uses an OpenVPN server and client; RMS downloads an OpenVPN configuration with private keys and certificates to the device; Teltonika's OpenVPN server allowed routing through it, giving access to everything the server could reach; researchers accessed AWS infrastructure, exfiltrated identification tokens and reached internal Teltonika services. — Claroty Team82
  • Teltonika wiki RUT241 Cloud Solutions, read 2026-11-21: RMS (Remote Management System) is a cloud system designed by Teltonika for remote monitoring and management of Teltonika-Networks products; RMS connection type Enabled | Standby | Disabled, default Enabled; Disabled means RMS functionality is completely disabled and no connection attempts are made. — Teltonika wiki
  • Not in the CISA KEV catalog, catalog version 2026.11.20 (1,790 entries), checked 2026-11-21. — CISA KEV
  • CVE record (checked 2026-11-21): state PUBLISHED, CNA CISA ICS (icscert), published 2023-05-22; CWE-918; CNA CVSS v3.1 5.8; affected Teltonika Remote Management System 0 before 4.10.0. — CVE.org
  • EPSS 0.00526, percentile 0.45488, dataset 2026-11-20, read 2026-11-21. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. CISA CSAF: ICSA-23-131-08 Teltonika Remote Management System and RUT Model Routers (machine-readable advisory)
  3. Claroty Team82: Triple Threat: Breaking Teltonika Routers Three Ways
  4. Teltonika wiki: RUT241 Cloud Solutions (RMS)
  5. CVE.org record CVE-2023-32348 (CNA: CISA ICS)
  6. CISA KEV
  7. FIRST EPSS

Frequently asked questions

What could an attacker reach through CVE-2023-32348?

Per CISA, other Teltonika devices connected to the RMS VPN hub. Claroty Team82 adds that routing through the OpenVPN server gave access to AWS infrastructure, identification tokens and internal Teltonika services.

Why is it classed as server-side request forgery?

CISA, the CNA, uses CWE-918 because the attacker makes Teltonika's OpenVPN server forward connections to destinations the attacker could not reach directly.

Do router owners need to update anything?

The RMS fix was applied server-side; CISA says the RMS services have already been updated. Teltonika recommends updating routers to the latest firmware (per CISA ICSA-23-131-08).

Is CVE-2023-32348 known to be exploited?

CISA reported no known public exploitation at publication, and it is not in the CISA KEV catalog as of 2026-11-21. FIRST EPSS gives it 0.00526 in the 2026-11-20 dataset.