CVE-2026-6901
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 · uneditedUntrusted Search Path vulnerability in B&R Industrial Automation GmbH APROL. This issue affects APROL: before R 4.4-01P5.
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 confidenceAPROL loads libraries or DLLs from locations that are not secured or validated, allowing potential attackers to place malicious libraries in the search path. This could lead to arbitrary code execution with the privileges of the APROL application.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.
-
Identify APROL installation locationLocate the APROL installation directory (commonly under C:\Program Files\B&R\APROL or similar B&R program directories). Check for the presence of the APROL application binaries and configuration files.Affected if APROL is installed in a directory that is writable by untrusted users or a shared/network location with limited access controls.
-
Determine installed APROL versionOpen the APROL configuration or About dialog, check the version information in the installation directory (often in a version.txt, readme, or executable properties), or query the APROL service/configuration for its version string.Affected if The installed version is earlier than R 4.4-01P5 (e.g., R 4.4, R 4.2, older versions).
-
Review system PATH environment variableOpen System Properties > Environment Variables and examine the PATH variable for user and system. Alternatively, run 'echo %PATH%' in command prompt. Inspect each directory listed.Affected if The PATH contains directories that are writable by untrusted users, temporary directories (Temp, tmp), network shares, or other untrusted locations.
-
Inspect APROL working directoryCheck the directory from which the APROL service or application is launched. This may be visible in service configuration (services.msc) or the startup configuration for the APROL process.Affected if APROL runs from a directory that is not a secured, vendor-provided installation path (e.g., runs from a user home directory or shared folder).
A system is affected if APROL version is earlier than R 4.4-01P5 AND the application runs from or loads libraries via directories accessible to untrusted 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.
From vendor dataUpgrade APROL to version R 4.4-01P5 or later. If upgrading is not immediately possible, ensure the application runs from trusted directories and that no untrusted locations are in the system PATH.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2026-6901 — 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-6901 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