Security readout for executives and security teams
Apache POI before 3.17 can be forced to hang or exhaust memory while processing specially crafted document and image-related formats. For businesses, the practical risk is service disruption in applications that parse uploaded or received Office-style files. The source bundle does not show data theft, data modification, or confirmed active exploitation. Exposure is most likely in applications or downstream products that embed Apache POI < 3.17 and parse untrusted documents, email messages, macros, or Office files. Public upload services, document conversion workflows, indexing pipelines, and backend automation are the highest concern when reachable by unauthenticated users. Prioritize remediation for internet-facing or business-critical document-processing systems. This is a high availability risk rather than a data breach indicator from the supplied sources, so urgency should track service criticality, external reachability, and whether untrusted files are processed automatically. Mitigation focus: Upgrade Apache POI to 3.17 or later where directly managed.; Apply vendor-supported package updates for products bundling Apache POI.; Review Red Hat and Oracle advisories for downstream patched versions..
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-835: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupCVE-2017-12626 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.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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:N/I:N/A:H3.93.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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
- RHSA-2018:1322CVE reference, apache · vendor-advisory, x_refsource_REDHAT
- [dev] 20180126 CVE-2017-12626 - Denial of Service Vulnerabilities in Apache POI < 3.17CVE reference, apache · mailing-list, x_refsource_MLIST
- [lucene-solr-user] 20190104 Re: SOLR v7 Security Issues Caused Denial of Use - Sonatype Application Composition ReportCVE reference, apache · mailing-list, x_refsource_MLIST
- https://www.oracle.com/security-alerts/cpuapr2020.htmlCVE reference, apache · x_refsource_MISC
- https://www.oracle.com/security-alerts/cpujul2020.htmlCVE reference, apache · x_refsource_MISC
- https://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.htmlCVE reference, apache · x_refsource_MISC
- https://www.oracle.com/security-alerts/cpujan2020.htmlCVE reference, apache · x_refsource_MISC
- https://www.oracle.com/security-alerts/cpuoct2020.htmlCVE reference, apache · x_refsource_MISC
- https://www.oracle.com/security-alerts/cpujan2021.htmlCVE reference, apache · x_refsource_MISC
- https://www.oracle.com/security-alerts/cpuApr2021.htmlCVE reference, apache · 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.
Loop with Unreachable Exit Condition ('Infinite Loop')
Loop with Unreachable Exit Condition ('Infinite Loop') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.