ZIP Bomb Detected Importing File<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } While importing an Excel file into the instance the following error is observed: *********** Name: ImportProcessor - loading CIPS file import (1 of 3) State: Complete Completion Code: Error Message: Com.glide.db.impex.datasource.DataSourceException:java.io.IOException: error in loading headers from the xlsx data source: Zip bomb detected! The file would exceed the max ratio of compressed file size to the size of the expanded data. This may indicate that the file used to inflate memory usage and thus could pose a security risk. You can adjust this limit via ZipSecureFile.setMininflateRatio() if you need to work with the files which exceed this limit. Counter: 2458533, cis.counter: 24576, ratio: 0.009996205053989514 Limits: MIN_INFLATE_RATIO: 0.01 *********** If you search for the term "Zip Bomb in Excel" on the internet you will come across the following definition/details: "A zip bomb, also known as a zip of death or decompression bomb, is a malicious archive file designed to crash or render useless the program or system reading it." Since the file in question is a Microsoft Excel file, the following information was also found in a Microsoft community article: Decompression Bomb in Excel filehttps://answers.microsoft.com/en-us/msoffice/forum/msoffice_excel-mso_winother-mso_2007/decompression-bomb-in-excel-file/856349d3-4b66-4174-b372-91c7b47458f3 Followed the steps posted under the "answer" of the post using 2 files; 12.2020 CIP Upload.xlsx (which generates the error) and CIP Upload 10.2020 .xlsx (which does not generate an error) Looking at the image below, one can see the image on the left is an Excel file that can be imported without any issue, and the image on the right is the file that generated the error, here I've highlighted the difference in the "styles.xml" and its size difference. In the image you can see that the file that has the styles.xml at 33kb is in the file whose total size is 880KB, thus I expect ALL the files contained in this Excel not to exceed the total size of the xlsx file upon decompressing. In the file that is generating the error, the styles.xml is 6.8 MB on its own. This is excel file size is 1.89 MB yet if it were to be decompressed it would be much larger. The issue above is not caused by the ServiceNow platform. The individual attempting the import would need to engage the original author of the Excel file to further investigate the issue.