Skip to main content
Menu
CVEs

CVE

LVRTC eParakstītājs SSRF and denial of service in eDOC file handling

CVE-2026-82951EUVD-2026-128600GHSA-J638-9Q8F-MGMPPublished Updated Summary written by a model

6.1MediumCNA
Exploited
No known exploitation
Fix
Fixed in 1.11.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 1.11.0.

Summary

LVRTC eParakstītājs 3.0 lets a remote attacker, without logging in, make a user's workstation send HTTP GET requests to loopback and private-network services, if the user opens a crafted signed eDOC file. The same file can also load local file URIs without limit, exhausting memory and causing a denial of service (OutOfMemoryError).

Original description

Latvijas Valsts radio un televīzijas centrs (LVRTC) eParakstītājs 3.0 version 1.10.0-resolute allows an unauthenticated remote attacker to cause HTTP GET requests from a user's workstation by convincing the user to open a crafted signed eDOC file. Automatic certificate validation retrieves a signer-controlled Authority Information Access (AIA) caIssuers URL and follows redirects without restricting the destination, enabling blind SSRF to loopback and private-network services. Additionally, unrestricted loading of local file URIs (such as file:///dev/zero) causes unbounded memory buffering resulting in Denial of Service (OutOfMemoryError). In automated server verification pipelines with UI:N, impact scales up to CVSS 8.6 High.

cve.now Index

13Pcve.now Index 13 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.1/10CVSS 6.1
  • No patch0/5No signal

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 28 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 1.11.0.

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-82951 (Blind SSRF in LVRTC eParakstītājs 3.0), 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-82951 (entry last updated 2026-11-18):
Affected:
- Latvijas Valsts radio un televīzijas centrs (LVRTC) eParakstītājs 3.0: from 1.10.0.1, fixed in 1.11.0
Fixed versions: 1.11.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-82951 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-82951 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://www.eparaksts.lv/lv/par_mums/Jaunumi/Jauna_eParakstitajs_30_versija_1_11
- https://br2sec.com/en/resources/cve-2026-82951-eparaksts-aia-ssrf/
- https://cvd.cert.lv//disclosed/vuln-lvrtc-772766932
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-82951
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-82951"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • 1.10.0-resolute

    From 1.10.0.1 · fixed in 1.11.0

Evidence 5

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-82951

Is CVE-2026-82951 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

Which versions are affected by CVE-2026-82951?

1.10.0-resolute: from 1.10.0.1 before 1.11.0.Source: cve.now feed data

How do I fix CVE-2026-82951?

Upgrade to a fixed version: 1.11.0.Source: cve.now feed data

More CVEs