Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain local device access
-
DeliveryCraft malicious _display_name argument
-
ExploitSubmit to Document Intake function
-
ExecutionTrigger path traversal in file creation
-
PersistWrite file outside temporary directory
-
ImpactLimited integrity/availability impact
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK
2 techniques across 2 tactics: Discovery, Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires LOCAL access to an Android device running Polaris Office App 9.9.19, plus the low-privilege ability (PR:L) to invoke the Document Intake function (com.infraware.service.m.n.a) with attacker-controlled input - for example a co-resident malicious app or a local user feeding a document whose _display_name carries traversal sequences. There is NO remote or network vector (AV:L) and no user interaction is modeled (UI:N). Exploitation is limited to writing files outside the designated temporary directory with only low integrity and low availability impact and no confidentiality disclosure; upgrading to version 9.9.22, which adds path validation, eliminates the condition. |
| Impact | This is a low-priority, low-real-risk issue despite having a public exploit. All signals align toward low severity: the CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:L/UI:N) confirms the attack requires LOCAL access and at least low privileges, not a remote network vector, and impact is limited to low integrity (VI:L) and low availability (VA:L) with NO confidentiality impact (VC:N). The input score of 1.9 (Low) is consistent with a constrained file-write path traversal rather than a code-execution or data-disclosure flaw. A POC is publicly available (hosted on Google Docs via VulDB), but there is NO EPSS score and NO CISA KEV listing provided, and absence of those is not evidence of exploitation - so this remains publicly available exploit code exists, not confirmed active exploitation. The local-only vector plus PR:L privilege requirement sharply limits realistic attack surface: an attacker must already be able to invoke the app's Document Intake function on the device. Note the source is VulDB (a third-party vulnerability database), not the vendor or NVD, though the vendor fix statement is quoted, lending credibility to the technical root cause. Net: genuine but minor bug; patch during routine update cycles rather than as an emergency. |
| Exploit ScenarioDerived | A malicious or compromised application on the same Android device supplies a crafted _display_name containing path traversal sequences to Polaris Office's Document Intake function (com.infraware.service.m.n.a), causing the app to create a file outside its designated temporary directory. A public POC exists (shared via a Google Docs link referenced by VulDB), but exploitation is local-only and limited to low-impact file write, not remote code execution. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Path traversal (CWE-22) in the Document Intake component of Polaris Office App 9.9.19 on Android lets a local, low-privileged actor write files outside the application's designated temporary directory by supplying a crafted _display_name value to com.infraware.service.m.n.a. There is no remote or network vector - exploitation requires local access to the device plus the low-privilege ability to invoke the Document Intake function (CVSS 3.1 AV:L/PR:L/UI:N), and the assessed impact is limited to low integrity and low availability with no confidentiality disclosure. A public exploit has been released (publicly available exploit code exists), but the risk is low: the vendor shipped a fix in version 9.9.22 that adds path validation, and the issue is not listed as confirmed actively exploited (CISA KEV) at time of analysis.
RemediationAI
Vendor-released patch: upgrade Polaris Office App for Android to version 9.9.22 or later from Google Play (https://play.google.com/store/apps/details?id=com.infraware.office.link); per the vendor, 9.9.22 adds path validation logic ensuring files are created only within the designated temporary directory, which removes the traversal condition. Because exploitation requires local access and a public exploit exists, prioritizing the update on devices used to open untrusted or third-party-supplied documents is prudent even though overall risk is low. Where immediate upgrading is not possible, compensating controls include avoiding the opening/intake of documents from untrusted sources whose display names may contain traversal sequences, and restricting or monitoring which local applications can bind to or invoke the com.infraware.office.link Document Intake service (for example via service/permission hardening or app-isolation tooling) - noting that such restrictions can break legitimate document-import and share-to-app workflows. No remote or network mitigation (such as port blocking or WAF rules) applies here, since the vector is strictly local (AV:L); the only durable fix is installing the 9.9.22 release.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is a classic absolute-path/directory traversal (CWE-22) inside an Android application service. The vulnerable entry point is the method com.infraware.service.m.n.a in the Document Intake component of com.infraware.office.link (Polaris Office App). When the application processes an intake document, it derives an output file name from the user-supplied _display_name field - the display-name column commonly populated via Android's MediaStore/ContentResolver when a document is picked or shared into the app. Because that value is concatenated into a file path without proper normalization or containment checks, traversal sequences (e.g., ../) allow the created file to escape the intended temporary directory and be written to an arbitrary location the app's sandbox permits. The root cause class is missing canonicalization/validation of a filename component before file creation; the vendor's own statement confirms this, noting that path validation logic was added so files are created only within the designated temporary directory. The CPE entry cpe:2.3:a:polaris:office_app:*:*:*:*:*:*:*:* identifies the Polaris Office Android application as the affected product family. The independent assessment maps the issue to CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L, i.e., a local attacker with low privileges and no user-interaction requirement, producing low integrity and low availability impact with no confidentiality loss and no scope change - consistent with the 1.9 base score reported for the v4.0 vector. Because the vector carries AV:L and PR:L, the issue is strictly local and requires some existing level of access (for example a co-resident malicious app invoking the service, or a local user feeding a document whose _display_name carries traversal sequences); there is no network attack surface.
Know when Office App gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
Local-only Android attack (AV:L) invoked through the app with low privilege (PR:L); constrained file-write yields low integrity/availability and no confidentiality, with no scope change.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
3DescriptionCVE.org
A security flaw has been discovered in Polaris Office App 9.9.19 on Android. Affected by this vulnerability is the function com.infraware.service.m.n.a of the component Document Intake. The manipulation of the argument _display_name results in path traversal. The attack is only possible with local access. The exploit has been released to the public and may be used for attacks. Upgrading to version 9.9.22 addresses this issue. It is recommended to upgrade the affected component. The vendor confirms: "We added path validation logic to ensure that files are created only within the designated temporary directory."
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
EUVD-2026-98317
GHSA-hjqm-98gp-r4v8
NVD
CVE.org
EPSS
VulDB
Exploit-DB