{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-62278 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-62278 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-62278 is a high-severity path traversal 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."},"fix_prompt":"Check this codebase for CVE-2026-62278 and fix it if it is affected.\n\nWhat it is: CVE-2026-62278 is a high-severity path traversal 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.\nExploitation: There is no known exploitation of CVE-2026-62278 in the wild and no public exploit code.\n\nAffected product: hargata lubelog. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-62278/ (Markdown: https://insights.sbomify.com/CVE-2026-62278/index.md)","id":"CVE-2026-62278","markdown":"https://insights.sbomify.com/CVE-2026-62278/index.md","name":"CVE-2026-62278","record":{"aliases":["GHSA-qm5x-mmwx-q7rm"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Vehicle maintenance tracker","requires_auth":"low_privilege","summary":"Authenticated users can exploit a path traversal flaw in LubeLogger to write files outside the intended directory, potentially leading to unauthorized file placement or code execution.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Path traversal in lubelog","id":"CVE-2026-62278","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Missing authorization in lubelog","id":"CVE-2026-62279"},"packages":[],"prev":{"headline":"OpenAM: WebAuthn Java deserialization RCE via ObjectInputFilter depth\u003e1 bypass","id":"CVE-2026-62263"},"products":["lubelog"],"published":"2026-09-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-21","vendors":["hargata"]},"summary":"Authenticated users can exploit a path traversal flaw in LubeLogger to write files outside the intended directory, potentially leading to unauthorized file placement or code execution.","url":"https://insights.sbomify.com/CVE-2026-62278/"}