CVE-2026-33277
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 OS command Injection issue exists in LogonTracer prior to v2.0.0. An arbitrary OS command may be executed by a logged-in user.
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 confidenceLogonTracer versions prior to v2.0.0 contain an OS command injection vulnerability that allows authenticated users to execute arbitrary operating system commands on the host, likely through unsanitized input being passed to system shell calls.
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< 2.0.0CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if LogonTracer is installedCheck for LogonTracer processes running on the system using 'ps aux | grep -i logontracer' or look for the application in common installation directories such as /opt, /usr/local, or the user's home directory. Also check if port 8080 or similar is listening, as LogonTracer typically runs a web interface.Affected if LogonTracer process or installation is found on the system
-
Determine the installed versionCheck the version of LogonTracer by examining the application itself. Look for a version file, check the web interface login page for version information, or run 'python -m logontracer --version' if the tool is installed as a Python module. If installed from source, check VERSION file or the main script for a version string.Affected if The version returned is less than 2.0.0 or no version can be determined (older installation)
-
Verify the service is accessible and runningConfirm the LogonTracer web service is listening and accessible. Check if the process is actively running and the web interface responds to HTTP requests. Use 'netstat -tuln' or 'ss -tuln' to identify listening ports associated with LogonTracer.Affected if The LogonTracer service is running and accessible on the network
You are affected if LogonTracer is installed and running with a version prior to v2.0.0, as this version range contains the OS command injection vulnerability that allows authenticated users to execute arbitrary OS commands.
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.
dbcve · scoped2.0.0
Upgrade LogonTracer to v2.0.0 or later to obtain the patched version that properly sanitizes user input before passing it to OS command execution functions.
2.0.0
- 1. Back up the current LogonTracer installation and any existing configuration files
- 2. Stop the LogonTracer service if it is currently running
- 3. Download LogonTracer version 2.0.0 or later from the official repository
- 4. Extract the new version to replace the existing installation files
- 5. Restore any custom configuration files from the backup if needed
- 6. Start the LogonTracer service
- 7. Verify the application is running correctly and the web interface is accessible
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33277 — 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-33277 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