CVE-2026-36726
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn arbitrary file deletion vulnerability in the /api/delete-temp-license/{file} endpoint of bookcars v8.3 allows unauthenticated attackers to delete arbitrary files via supplying directory traversal sequences.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAn unauthenticated path traversal vulnerability in the /api/delete-temp-license/{file} endpoint of bookcars v8.3 allows attackers to delete arbitrary files on the server by supplying directory traversal sequences (e.g., ../../) in the file parameter.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm bookcars installation and versionInspect application files (e.g., package.json, version file) or query the application's version endpoint to identify if bookcars version 8.3 or lower is installedAffected if bookcars version 8.3 or lower is confirmed
-
Identify if the delete-temp-license endpoint existsReview application routing configuration or source code to determine if the /api/delete-temp-license/{file} endpoint is defined and exposedAffected if The endpoint is present in the application routes
-
Verify endpoint authentication requirementsExamine the endpoint handler code or middleware configuration to determine if the /api/delete-temp-license endpoint enforces authentication or authorization checks before processing requestsAffected if The endpoint does not require valid authentication credentials
-
Check input validation on the file parameterReview the endpoint handler code to inspect how the file parameter is processed and whether directory traversal sequences (../, ..\) are validated, rejected, or sanitized before being used in file operationsAffected if The file parameter accepts directory traversal sequences without validation or sanitization
The environment is affected if bookcars version 8.3 or lower is running, the /api/delete-temp-license endpoint is exposed, no authentication is required, and the file parameter accepts unsanitized directory traversal sequences.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict input validation to reject directory traversal sequences and ensure the endpoint requires proper authentication before allowing file operations.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36726 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-36726 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data