Security readout for executives and security teams
Plain-English summary
Vertex before the fixed commit has a path traversal flaw. An attacker on the network may be able to access files outside intended paths, creating high confidentiality risk with some integrity and availability impact. The source bundle identifies a specific fixing commit but does not provide broader workaround details.
Executive priority
Treat this as a high-priority patching item where Vertex is deployed. The main business risk is unauthorized file access from a remotely reachable management tool. Urgency is highest for internet-facing or broadly accessible instances.
Technical view
CVE-2024-40646 is a CWE-22 path traversal vulnerability in vertex-app Vertex before commit fbde301b97986d5913fc4bc95f5445750d282e11. CVSS 3.1 is 8.6 with network attack vector, low complexity, no privileges, and no user interaction. Impacts are high confidentiality, low integrity, and low availability.
Likely exposure
Exposure is limited to organizations running Vertex versions older than commit fbde301b97986d5913fc4bc95f5445750d282e11, especially if reachable over untrusted networks. The bundle does not list CPEs, package coordinates, hosted service exposure, or affected release numbers.
Exploitation context
The CVSS vector indicates remote, unauthenticated exploitation is plausible in affected deployments. The provided sources do not state active exploitation, and KEV is false. No public exploit status is established by this bundle.
Researcher notes
Evidence is concise and source-limited: the advisory states path traversal before the fixed commit, and CVSS defines remote unauthenticated characteristics. The bundle does not describe affected endpoints, proof-of-concept details, workaround controls, exploit maturity, or affected releases beyond the commit boundary.
Mitigation direction
- Upgrade Vertex to a version containing commit fbde301b97986d5913fc4bc95f5445750d282e11.
- Review the GitHub advisory for vendor release and upgrade guidance.
- Do not rely on unverified workarounds as a substitute for the fixed commit.
- Prioritize exposed Vertex deployments for remediation first.
Validation and detection
- Inventory all Vertex deployments and record their release or commit identifier.
- Confirm deployed code includes commit fbde301b97986d5913fc4bc95f5445750d282e11 or later.
- Check whether Vertex is reachable from untrusted networks.
- Review logs for unusual file access indicators, if available.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2024-40646 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L3.94.7GitHub_MVulnerability scoring details
Base CVSS 3.1 score
8.6HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/vertex-app/vertex/security/advisories/GHSA-92j5-qc36-23rrCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/vertex-app/vertex/commit/fbde301b97986d5913fc4bc95f5445750d282e11CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.