dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-36829

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
An authentication bypass vulnerability exists in the embedded HTTP server of Panabit PAP-XM320 up to and including v7.7. The server validates session cookies using a filesystem existence check based on a user-controlled cookie value without proper sanitization, allowing directory traversal and bypass of authentication.

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 confidence

Authentication bypass in Panabit PAP-XM320 embedded HTTP server where session cookie validation relies on filesystem existence checks using user-controlled cookie values without sanitization, enabling directory traversal to bypass authentication.

MitigationApply available patches from vendor; if no patch exists, restrict network access to the HTTP server or implement additional authentication controls as a compensating control.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Panabit PAP-XM320 hardware or software installation
    Locate the device or software by checking system inventory, network scans for Panabit devices, or reviewing installed software lists for 'Panabit' or 'PAP-XM320' identifiers.
    Affected if The system is not a Panabit PAP-XM320 device or software, then it is not affected by this specific CVE.
  2. Determine the installed Panabit version
    Access the device management interface or check system files for the firmware/software version. Common locations include: system status page, version info in the admin panel, or files like /etc/version or /opt/panabit/version on the device.
    Affected if The installed version is earlier than v7.7. Versions prior to v7.7 contain the vulnerable cookie handling code.
  3. Verify the embedded HTTP server is enabled
    Check the Panabit configuration for HTTP server settings. This may be accessible via the admin web interface under services/network settings, or by examining configuration files for HTTP server enable flags.
    Affected if The embedded HTTP server is disabled or not in use, the vulnerability cannot be exploited through this attack vector.
  4. Inspect cookie handling configuration
    Examine the HTTP server configuration files or session management settings for how cookie values are processed. Look for parameters controlling session validation and path checking mechanisms.
    Affected if The configuration allows arbitrary cookie values to be used in filesystem existence checks without sanitization, the system is vulnerable.
  5. Check for recent authentication logs or access patterns
    Review HTTP server access logs for unusual cookie patterns containing '../' sequences or attempts to access unexpected file paths via cookie manipulation.
    Affected if Evidence exists of directory traversal attempts in cookie parameters, this indicates active exploitation or probing of the vulnerability.

You are affected if the system is a Panabit PAP-XM320 device running the embedded HTTP server with a version earlier than v7.7 where cookie values are used for filesystem-based session validation without input sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply available patches from vendor; if no patch exists, restrict network access to the HTTP server or implement additional authentication controls as a compensating control.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA6.0 h
32.0 hours of engineering $5,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,024.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-36829 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-36829 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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