CVE-2023-26077
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 · uneditedAtera Agent through 1.8.3.6 on Windows Creates a Temporary File in a Directory with Insecure Permissions.
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 confidenceThe Atera Agent through version 1.8.3.6 on Windows creates temporary files in a directory with insecure permissions, allowing local unprivileged users to potentially manipulate these files for privilege escalation to SYSTEM level.
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< 1.8.3.7CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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.
-
Confirm Atera Agent installationCheck for Atera Agent in installed programs list (Control Panel > Programs and Features, or run: Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like '*Atera*'})Affected if Atera Agent is listed as installed on the system
-
Identify installed Atera Agent versionCheck the installed version via Windows Programs and Features, or inspect the Atera Agent installation directory for version informationAffected if The installed version is 1.8.3.6 or lower (any version prior to 1.8.3.7)
-
Locate Atera temporary directoryExamine the Atera Agent installation folder for temporary file storage locations (typically under the main installation path in AppData or Program Files)Affected if Atera creates a temporary directory with weak permissions that allows unprivileged users to modify contents
-
Check temporary directory permissionsReview the permissions on the identified temporary directory (right-click > Properties > Security tab, or use: Get-Acl 'path_to_temp_directory' | Select-Object AccessToString)Affected if The directory grants write/modify access to Users group or other unprivileged accounts, allowing manipulation of temporary files
-
Verify if Atera Agent service runs with elevated privilegesCheck the Atera Agent service configuration in Services.msc or via: Get-Service -Name '*Atera*' | Select-Object Name, Status, StartTypeAffected if The service runs under SYSTEM or another high-privilege account, creating a privilege escalation path if temporary files can be manipulated
A system is affected if Atera Agent version 1.8.3.6 or lower is installed and creates temporary files in a directory with insecure permissions accessible to unprivileged users.
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 · scoped1.8.3.7
Update Atera Agent to a patched version once available, or remediate by restricting permissions on the affected temporary directory to prevent unauthorized user access.
Atera Agent version 1.8.3.7 or later
- Identify the current Atera Agent version installed on Windows systems
- Access the Atera admin console or use the built-in update mechanism to update the Atera Agent
- Update to version 1.8.3.7 or later which contains the security fix for the insecure temporary file permissions vulnerability
- Verify the updated version is 1.8.3.7 or higher after the update completes
- Confirm that the temporary files created by the Atera Agent now have appropriate secure permissions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-26077 — 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-2023-26077 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