LubeLogger is a self-hosted, open-source, web-based vehicle maintenance and fuel mileage tracker. Prior to 1.6.8, an authenticated user could submit caller-controlled recordIds to the DuplicateRecordsToOtherVehicles endpoint while naming destination vehicleIds the user could edit. The endpoint authorized the destination vehicles but fetched source records in Controllers/VehicleController.cs without checking UserCanEditVehicle for each existingRecord.VehicleId. This missing source-vehicle authorization allowed service, collision, upgrade, fuel, tax, supply, note, odometer, reminder, plan, inspection, and equipment records belonging to another user to be copied into an attacker-controlled vehicle, exposing record contents and attachment paths and creating persistent copies. This issue is fixed in version 1.6.8.
CVE-2026-62279
This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 70% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(medium)
- EG Risk
- 37(Track)EG Risk 37/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity71% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 30%
- KEV
- Not listed
Published
September 18, 2026
Last Modified
September 18, 2026
Advisory Details (5)
Auto-updated Sep 18, 2026Version 1.6.8
Patch available: hargata/lubelog v1.6.8
https://github.com/hargata/lubelog/releases/tag/v1.6.8commit c8d5888ebc69 (hargata/lubelog)
Patch available: hargata/lubelog v1.6.8 (contains commit c8d5888ebc69)
https://github.com/hargata/lubelog/commit/c8d5888ebc69e6a163e33f36200233ec845e5c57fixes path traversal/idor vulnerabilities
Patch available: hargata/lubelog v1.6.8 (PR #1395 merged 2026-06-25)
https://github.com/hargata/lubelog/pull/1395Fix CVEs · Issue #1398 · hargata/lubelog · GitHub
https://github.com/hargata/lubelog/issues/1398IDOR in DuplicateRecordsToOtherVehicles Allows Copying Records from Any User's Vehicle Without Ownership Check · Advisory · hargata/lubelog · GitHub
https://github.com/hargata/lubelog/security/advisories/GHSA-3r34-mx83-q67rWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-21 05:17 UTCEG score recompute
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-19 17:57 UTCEG score recompute
- 2026-09-18 18:27 UTCEG score recompute
- 2026-09-18 17:19 UTCEG score recompute
- 2026-09-18 17:19 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
Frequently asked(5)
What is CVE-2026-62279?
When was CVE-2026-62279 disclosed?
Is CVE-2026-62279 actively exploited?
What is the CVSS score of CVE-2026-62279?
How do I remediate CVE-2026-62279?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-62279
Is Your Infrastructure Affected by CVE-2026-62279?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.