dbcve.org
IstaxApplication · Microchip

CVE-2026-2336

HIGH · 8.8 CVSS v3.1 Published 2026-04-16
Fix available
A fix is available. Upgrade to 2026.03 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
A privilege escalation vulnerability in Microchip IStaX allows an authenticated low-privileged user to recover a shared per-device cookie secret from their own webstax_auth session cookie and forge a new cookie with administrative privileges.This issue affects IStaX before 2026.03.

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 · moderate confidence

A privilege escalation vulnerability in Microchip IStaX allows an authenticated low-privileged user to recover a shared per-device cookie secret from their webstax_auth session cookie and forge new cookies with administrative privileges. The issue stems from predictable or recoverable cryptographic secrets in the session cookie mechanism.

MitigationUpgrade IStaX to version 2026.03 or later which addresses the cookie secret exposure and privilege escalation vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
IstaxApplication
Affected:< 2026.03

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm product is Microchip IStaX
    Identify if the web application or appliance running is Microchip IStaX. Check the product name in the UI, system information, or documentation.
    Affected if The product is Microchip IStaX and version is before 2026.03
  2. Determine installed IStaX version
    Locate the version information for your IStaX installation. This is typically accessible via the web UI footer, help/about section, system settings, or command line interface if available.
    Affected if The installed version is any version prior to 2026.03 (the fixed release)
  3. Examine webstax_auth session cookie
    Log in as a low-privileged user and inspect the webstax_auth cookie in your browser developer tools or via network traffic capture. Note the cookie value structure and whether it appears obfuscated or contains predictable patterns.
    Affected if The cookie value can be decoded, reversed, or shows low entropy/reproducible patterns that could reveal the underlying secret
  4. Test cookie forgery potential
    Using the recovered or analyzed cookie secret from the webstax_auth cookie, attempt to construct a modified cookie with elevated privileges (such as admin or administrator role) and submit it in a request.
    Affected if You can successfully forge a cookie granting higher privileges than your authenticated session normally permits
  5. Check for unauthorized admin sessions
    Review server logs, session tables, or active user lists for sessions with administrative privileges that were created by users who should only have low-level access.
    Affected if Low-privileged users have active sessions with administrative roles

Your environment is affected if you are running any version of Microchip IStaX prior to 2026.03 and the webstax_auth session cookie contains recoverable or predictable cryptographic secrets that allow privilege escalation.

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.

dbcve · scoped
Upgrade available Upgrade to 2026.03 or later
Fixed in 2026.03
Interim mitigation

Upgrade IStaX to version 2026.03 or later which addresses the cookie secret exposure and privilege escalation vulnerability.

Recommended fix Moderate confidence

IStaX 2026.03 or later

  1. 1. Verify the current IStaX installation version through the web interface or CLI documentation
  2. 2. Download the IStaX 2026.03 or later release from Microchip's official support portal or download center
  3. 3. Review the upgrade instructions in the IStaX release notes or upgrade guide
  4. 4. Perform a full backup of the current IStaX configuration and data
  5. 5. Apply the upgrade following Microchip's documented upgrade procedure
  6. 6. After upgrade, verify that the webstax_auth cookie mechanism has been updated
  7. 7. Confirm that low-privileged users can no longer forge administrative session cookies
Caveat Review release notes for any configuration changes or backward compatibility considerations when upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Istax Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2336 — 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-2336 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