CVE-2026-62278: LubeLogger: Path Traversal in HandleTranslationFileUpload Allows Authenticated Users to Write Files Outside Data Directory

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-04 15:41 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

LubeLogger is a self-hosted, open-source, web-based vehicle maintenance and fuel mileage tracker. Prior to 1.6.8, authenticated non-administrative users could reach HandleTranslationFileUpload and influence the name passed from Controllers/FilesController.cs to RenameFile in Helper/FileHelper.cs. RenameFile constructed newFilePath with string replacement and moved the uploaded file without verifying the resolved absolute path remained under the web root or data directory. A crafted upload name could therefore move an uploaded file outside the intended storage directory, enabling unauthorized file placement or overwrite with the privileges of the application process. This issue is fixed in version 1.6.8.

Description quoted from the CVE record (assigned by GitHub_M, published 2026-09-18).

Weakness: CWE-22: Improper Limitation of a Pathname to a Restricted Directory (‘Path Traversal’)

How it can be exploited

Exploitable over the network with low attack complexity needing low privileges and no user interaction. Impact: confidentiality high, integrity high, availability none. CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: total.

Public exploit evidence (Exploit Observer)

Exploit Observer found 3 code repositories naming this CVE.

Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.

See all 5 references on Exploit Observer

Live scores

EPSS
0.005
low predicted chance of attack
VEDAS
0.986
strong exploit evidence
On CISA KEV
Not listed
Detection rule
Suricata

Who is affected

ProductAffectedNot affected
hargata lubelogversion < 1.6.8Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.

How to detect it

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-62278 LubeLogger - Path Traversal via translation file upload filename. Add them to your Suricata rule set and reload.

Show the rules
suricata
# CVE-2026-62278 - LubeLogger < 1.6.8 path traversal in the translation file upload
# (FilesController.HandleTranslationFileUpload -> FileHelper.RenameFile). The uploaded file
# name is used to build the destination path without base-name reduction, so a name with
# ../ escapes the storage directory. Matches the authenticated multipart POST whose
# filename contains traversal sequences.
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-62278 LubeLogger - Path Traversal via translation file upload filename"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/Files/HandleTranslationFileUpload"; nocase; fast_pattern; http.request_body; content:"filename="; nocase; pcre:"/filename=\x22?[^\x22\r\n]*(?:\x2e\x2e\x2f|\x2e\x2e\x5c|\x2e\x2e%2f)/i"; classtype:web-application-attack; reference:cve,CVE-2026-62278; reference:url,https://www.exploit.observer/?keyword=CVE-2026-62278&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=lubelogger&match=exact; sid:1100202; rev:1;)

CVE-2026-62278.rules on GitHub

References

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.

Supporting partners

Feasible SecurityAskealGoTrust