# CVE-2026-62279: LubeLogger missing authorization in vehicle record duplication

Source: https://junglewise.ai/threats/cve-2026-62279-lubelogger-is-a-self-hosted-open-source-web-based-vehicle  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-18. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-62279 · Severity: high · CVSS 7.1 · Published 2026-09-18

LubeLogger is a self-hosted web application for tracking vehicle maintenance, fuel costs, and repairs. An authenticated user could exploit a missing authorization check to copy maintenance and service records (including attachments and sensitive paths) from other users' vehicles into their own account, exposing private vehicle history and creating persistent unauthorized copies.

Technologies: [Hargata LubeLogger](https://junglewise.ai/threats/technologies/lubelogger). Vendors: [Hargata](https://junglewise.ai/threats/vendors/hargata).

## Quick answers

**Is CVE-2026-62279 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-62279 being exploited in the wild.

**How severe is CVE-2026-62279?** High severity, with a CVSS score of 7.1, published 18 September 2026.

**Which products and versions are affected?** Hargata LubeLogger before 1.6.8.

**Is there a fix for CVE-2026-62279?** A patch was published on 2026-06-25: Fix committed to main branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-62279 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-62279?** Check whether you run Hargata LubeLogger at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The DuplicateRecordsToOtherVehicles endpoint in VehicleController.cs authorizes the destination vehicle but fails to validate that the authenticated user owns the source vehicle before copying records. This insecure direct object reference (IDOR) vulnerability allows an authenticated attacker to enumerate and duplicate service, fuel, tax, supply, note, odometer, reminder, plan, inspection, and equipment records across vehicles without proper access control.

## Affected products

- hargata LubeLogger before 1.6.8

## Timeline

- 2026-06-25: patched: Fix committed to main branch
- 2026-09-18: disclosed

## References

- [https://github.com/hargata/lubelog/commit/c8d5888ebc69e6a163e33f36200233ec845e5c57](https://github.com/hargata/lubelog/commit/c8d5888ebc69e6a163e33f36200233ec845e5c57)
- [https://github.com/hargata/lubelog/issues/1398](https://github.com/hargata/lubelog/issues/1398)

## Related threats

- [LubeLogger insecure direct object reference in PrintRecordStickers](https://junglewise.ai/threats/cve-2026-62277-lubelogger-is-a-self-hosted-open-source-web-based-vehicle)
- [LubeLogger path traversal in translation file upload](https://junglewise.ai/threats/cve-2026-62278-lubelogger-is-a-self-hosted-open-source-web-based-vehicle)