# CVE-2026-62279: Missing authorization in lubelog

> Authenticated attackers can copy other users' vehicle records to their own vehicles due to missing source ownership checks, exposing sensitive data.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-3r34-mx83-q67r

## What is CVE-2026-62279?

CVE-2026-62279 is a high-severity missing authorization vulnerability in hargata lubelog, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-62279?


## How do I fix CVE-2026-62279?

No fix has been published for CVE-2026-62279 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-62279 being exploited?

There is no known exploitation of CVE-2026-62279 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-62279 and fix it if it is affected.

What it is: CVE-2026-62279 is a high-severity missing authorization vulnerability in hargata lubelog, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-62279 in the wild and no public exploit code.

Affected product: hargata lubelog. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-62279/ (Markdown: https://insights.sbomify.com/CVE-2026-62279/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-62279
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-62279
- OSV: https://osv.dev/vulnerability/CVE-2026-62279

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-62279/
Summaries are generated and may contain mistakes; the official description above is the record.