dbcve.org
Automotive Grade LinuxOperating system · Linuxfoundation

CVE-2026-37531

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-01
Fix available
A fix is available. Upgrade to after 17.1.12 or later.
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
AGL app-framework-main thru 17.1.12 contains a Zip Slip path traversal vulnerability (CWE-22) combined with a TOCTOU race condition (CWE-367) in the widget installation flow. The is_valid_filename function in wgtpkg-zip.c validates ZIP entry names but does not check for dot notation directory traversal sequences it only blocks absolute paths. The zread extraction function uses openat(workdirfd, filename, O_CREAT) which resolves dot notation values relative to the work directory, allowing files to be written anywhere on the filesystem. Critically, in function install_widget in file wgtpkg-install.c, extraction via zread occurs BEFORE signature verification via check_all_signatures. Even if signature verification fails, the error cleanup (remove_workdir) only deletes the temporary work directory files written outside via path traversal persist permanently.

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

AGL app-framework-main through version 17.1.12 has a critical path traversal vulnerability in widget installation where is_valid_filename in wgtpkg-zip.c only blocks absolute paths but not dot notation traversal sequences, allowing the zread extraction function to write files anywhere via openat with relative paths. Additionally, a TOCTOU race condition exists because widget extraction via zread occurs before signature verification via check_all_signatures, and failed verification cleanup does not remove files already written outside the work directory.

MitigationReorder operations to verify widget signatures BEFORE extraction; enhance is_valid_filename to reject all path traversal sequences including dot notation; implement comprehensive cleanup that tracks and removes any files written outside the intended work directory upon verification failure.

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
Automotive Grade LinuxOperating system
Affected:<= 17.1.12

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 installed version of app-framework-main
    Query the package manager or inspect the installed app-framework-main version (e.g., rpm -q, dpkg -l, or check /usr/lib version files depending on the AGL distribution)
    Affected if The installed version is 17.1.12 or any earlier version (versions <= 17.1.12 are affected)
  2. Verify widget installation feature status
    Check if widget installation functionality is enabled in the AGL system configuration or service status (look for widget-related services or configuration files in the app-framework setup)
    Affected if Widget installation is enabled and the version is <= 17.1.12 - the path traversal vulnerability is present in the wgtpkg-zip.c component used during widget processing
  3. Inspect is_valid_filename implementation in wgtpkg-zip.c
    If accessible, examine the source file wgtpkg-zip.c and locate the is_valid_filename function - verify whether it only checks for absolute paths or also blocks dot notation sequences (..)
    Affected if The function only rejects absolute paths but allows ../ or .. sequences - the vulnerability exists
  4. Check signature verification timing in widget installation flow
    Review the widget installation code flow to determine whether zread (extraction) occurs before check_all_signatures (verification) - this may require code inspection or configuration analysis
    Affected if Extraction happens before signature verification - the TOCTOU race condition is present

A user is affected if app-framework-main version is 17.1.12 or earlier AND widget installation is enabled, since both the path traversal flaw in is_valid_filename and the TOCTOU vulnerability in extraction-versus-verification ordering exist in these versions.

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 a release after 17.1.12
Interim mitigation

Reorder operations to verify widget signatures BEFORE extraction; enhance is_valid_filename to reject all path traversal sequences including dot notation; implement comprehensive cleanup that tracks and removes any files written outside the intended work directory upon verification failure.

Recommended fix Moderate confidence

version > 17.1.12 (check AGL release notes for the specific fixed release)

  1. 1. Upgrade app-framework-main to a version beyond 17.1.12 that includes the fix for the Zip Slip path traversal vulnerability
  2. 2. If an official fixed release is not yet available, apply any vendor-supplied patches referenced in the AGL gerrit repository
  3. 3. As a temporary mitigation, restrict widget installation permissions to trusted sources only
  4. 4. Ensure signature verification occurs before any file extraction begins in the installation workflow
  5. 5. Implement additional validation to block dot notation directory traversal sequences (..) in addition to absolute paths
  6. 6. Verify that error cleanup properly removes any files written outside the intended work directory

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

Fix this in Automotive Grade Linux Scoped from the published advisory
  • Consultation6.0 h
  • Implementation20.0 h
  • Testing12.0 h
  • Review / QA6.0 h
44.0 hours of engineering $7,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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