Skip to main content

CVE-2026-87789Latvijas Valsts radio un televīzijas centrs (LVRTC) eParakstītājs 3.0 external control of a file name

Schedule itHigh8.6EPSS not scored yet

CVE-2026-87789 is a external control of a file name in Latvijas Valsts radio un televīzijas centrs (LVRTC) eParakstītājs 3.0, rated high (8.6 on CVSS 4.0).

Why this priority: High severity, with no exploitation signal yet.

Published · Updated · NVD status: Received

What it is

Input decides which file the software opens, so a caller can point it elsewhere. Input reaches an operating-system command line, letting an attacker run their own commands on the host.

How it is reached

An attacker can exploit it over the network, without an account, but someone has to act first, such as opening a file or following a link.

What an attacker gains

A successful attack can read the data it protects, change data or behaviour and take it offline. In practice, this kind of flaw lets an attacker read or write files outside the folders the service meant to expose.

Is it being exploited?

There is no public report of exploitation yet.

What to do

  1. Upgrade Latvijas Valsts radio un televīzijas centrs (LVRTC) eParakstītājs 3.0 to 1.11.0 or later.
  2. Until it is patched, keep it off the internet or behind a VPN, allowlist or authenticating proxy.
  3. Warn the people who use it, and filter files and links on the way in.

Description from NVD

Latvijas Valsts radio un televīzijas centrs (LVRTC) eParakstītājs 3.0 version 1.10.0 for macOS allows an unauthenticated remote attacker to execute arbitrary commands with the privileges of the current user by convincing the user to open a PDF with a crafted filename and select Send. The application embeds the attachment path in AppleScript source without neutralizing AppleScript syntax, allowing injected do shell script expressions to execute.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • File storage the service can read or write. The flaw sits between the application and the file system it can reach.
  • Application servers and the hosts they run on. The flaw sits between untrusted input and code or command execution.
  • Template engines. The flaw sits between untrusted input and code or command execution.
  • Web front ends and single-page apps. The flaw sits between a user's browser and the web application.

Trust boundaries in play

  • Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
  • People who open files and links. Mail, chat and browsers are the delivery path.
  • Between the application and the file system it can reach. An attacker who crosses it can read or write files outside the folders the service meant to expose.
  • Between untrusted input and code or command execution. An attacker who crosses it can run commands or code with the privileges of the affected service.

Questions to answer about your own systems

  • Where does Latvijas Valsts radio un televīzijas centrs (LVRTC) eParakstītājs 3.0 run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.