This is an automated email from the ASF dual-hosted git repository.
pjfanning pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/poi.git
The following commit(s) were added to refs/heads/trunk by this push:
new 49790d48d1 Update security.xml
49790d48d1 is described below
commit 49790d48d17636e7c8e284fbbef7a675de5c52a8
Author: PJ Fanning <[email protected]>
AuthorDate: Fri Jun 5 17:42:18 2026 +0100
Update security.xml
---
src/documentation/content/xdocs/security.xml | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/src/documentation/content/xdocs/security.xml
b/src/documentation/content/xdocs/security.xml
index a7a9596c44..b3b7a31e7f 100644
--- a/src/documentation/content/xdocs/security.xml
+++ b/src/documentation/content/xdocs/security.xml
@@ -107,6 +107,14 @@
strategy implementation. It is possible to configure POI to
avoid temp file usage in some parts of
the code.
</li>
+ <li><strong>Heap Memory</strong><br/>
+ Apache POI can have sensitive sensitive data from parsed or
generated documents in memory.
+ Classes like <em>Biff8EncryptionKey</em> use ThreadLocal to
store sensitive data. Users should ensure
+ that they clear this data as soon as possible after use.
+ <br/>
+ It is strongly recommended that POI based code is not run in a
JVM where untrusted users have access to
+ the heap memory, e.g. by using a shared hosting environment.
+ </li>
<li><strong>Consider sandboxing document-parsing</strong><br/>
If you operate in a highly sensitive environment and would
like to avoid any side effect from
parsing documents on your application, then consider
extracting the parsing logic into a separate
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]