PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-112049 Vita3K CVE debrief

A path traversal vulnerability exists in Vita3K before build 4187, allowing attackers to write files outside the install directory via crafted .vpk archives. This vulnerability can be exploited by embedding '..' segments or absolute paths in zip entry names, potentially enabling host code execution. Defenders should assess exposure and prioritize verification and updates to prevent potential code execution and data tampering. The vulnerability is caused by a path traversal issue in the install_archive_content() function, which allows attackers to write files outside the install directory.

Vendor
Vita3K
Product
Vita3K
CVSS
MEDIUM 6.7
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-18
Original CVE updated
2026-10-18
Advisory published
2026-10-18
Advisory updated
2026-10-18

Who should care

Defenders responsible for Vita3K installations should assess exposure and prioritize verification and updates to prevent potential code execution and data tampering. This includes operators, platform administrators, vulnerability management teams, and security teams. They should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.

Why it matters

Defenders should prioritize verifying and updating Vita3K installations to prevent potential code execution and data tampering.

  • Potential code execution on affected systems
  • Data tampering or unauthorized file writes
  • Elevation of privileges on affected systems
  • Verification of Vita3K installations and updates required

Technical summary

The vulnerability exists in the install_archive_content() function, which allows attackers to write files outside the install directory via crafted .vpk archives. This can be exploited by embedding '..' segments or absolute paths in zip entry names, potentially enabling host code execution. The issue is limited to Vita3K before build 4187. Defenders should prioritize verifying and updating Vita3K installations to prevent potential code execution and data tampering. The CVE record and NVD vulnerability detail page provide additional information.

Defensive priority

Defenders should prioritize verifying and updating Vita3K installations to prevent potential code execution.

Recommended defensive actions

  • Verify Vita3K installations and update to build 4187 or later
  • Restrict write access to Vita3K installation directories
  • Monitor Vita3K installations for suspicious activity
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is caused by a path traversal issue in the install_archive_content() function, which allows attackers to write files outside the install directory via crafted .vpk archives. The issue is limited to Vita3K before build 4187. Defenders should verify and update Vita3K installations to prevent potential code execution. Evidence is based on the CVE record and NVD vulnerability detail page.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-112049 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-112049

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-112049 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-112049

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.