Security readout for executives and security teams
Plain-English summary
Arcane before 1.19.4 lets an authenticated user make the backend read arbitrary host files through Docker Compose include handling. Sensitive files could include Arcane’s own database, exposing password hashes and API keys. Because Arcane controls Docker resources, account escalation could lead to serious host compromise.
Executive priority
Treat as high priority for any Arcane instance with multiple users or important Docker access. Patch promptly, then assess whether sensitive Arcane credentials may have been read before the upgrade.
Technical view
The flaw is a path traversal issue in ProjectService.GetProjectFileContent and CreateProject. Attacker-supplied compose content can reference include paths before traversal validation occurs, allowing reads of files accessible to the Arcane backend process. The advisory rates this CVSS 7.7 and says version 1.19.4 fixes it.
Likely exposure
Exposure is limited to Arcane deployments before 1.19.4 where authenticated users can create or modify projects. Risk is higher if Arcane is reachable by many users or manages privileged Docker access on important hosts.
Exploitation context
Sources describe a network-accessible, low-privilege authenticated attack requiring no user interaction. The bundle does not cite active exploitation, and KEV status is false. Impact is primarily confidentiality, but disclosed credential material could enable administrative escalation and Docker control-plane abuse.
Researcher notes
Evidence comes from the CVE record, GitHub advisory, and fix commit. The bug is the ordering of include resolution before path validation, combined with accepting attacker-supplied compose content. No cited source proves exploitation in the wild.
Mitigation direction
- Upgrade Arcane to version 1.19.4 or later.
- Restrict project creation and compose editing to trusted users.
- Review vendor advisory guidance before changing operational controls.
- Rotate Arcane API keys if database exposure is suspected.
- Reset affected user passwords if password hashes may have been exposed.
Validation and detection
- Inventory Arcane instances and confirm each version is 1.19.4 or later.
- Review project compose files for unexpected include directives.
- Check project creation and file-read activity for suspicious authenticated access.
- Confirm only trusted users can create or modify Arcane projects.
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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-47179 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
- 7.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
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:L/UI:N/S:C/C:H/I:N/A:N3.14GitHub_MVulnerability scoring details
Base CVSS 3.1 score
7.7HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
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/getarcaneapp/arcane/security/advisories/GHSA-c3px-h233-h6fqCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/getarcaneapp/arcane/commit/b6cbffabf61dbc3f12a28d3b5830e3c6b7e67dafCVE 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.