(velocity-site) branch main updated: Add Security Model section to landing page

[cb...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

cbrisson pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/velocity-site.git


The following commit(s) were added to refs/heads/main by this push:
     new f5ef14c2 Add Security Model section to landing page
f5ef14c2 is described below

commit f5ef14c227d23f58733e12ce5b2de336e6f07632
Author: Claude Brisson <cl...@renegat.net>
AuthorDate: Wed Mar 25 11:53:57 2026 +0100

    Add Security Model section to landing page
---
 src/content/index.mdtext | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/src/content/index.mdtext b/src/content/index.mdtext
index ead64359..5dab5466 100644
--- a/src/content/index.mdtext
+++ b/src/content/index.mdtext
@@ -42,6 +42,16 @@ Velocity Tools | [3.1](tools/3.1) | (currently none available)
 
 The release distribution is available as a combined source/binary distribution in tar.gz and zip formats, and can be downloaded from [our download page](/download.cgi).
 
+## Security Model
+
+### Templates Loading
+
+Velocity Engine and Velocity Tools rely on the template loaders defined in the `velocity.properties` configuration file and/or properties defined in the webapp descriptor or web container configuration. If those configurations are compromised, Velocity cannot ensure that templates do not come from a malicious source. This is **NOT** a Velocity vulnerability. If the attacker is already in control of the web application configuration files, they already have far more powerful attack vector [...]
+
+### Velocity Context
+
+Velocity Engine provides a SecureUberspector helper class which helps ensure that the Velocity context does not contain any dangerous class in a user-facing template editing scenario. But this class and its configuration are just provided as *a starting point*: Velocity cannot know in advance how the Velocity context is populated and cannot possibly ban all potentially dangerous classes. It is the responsibility of the application authors to audit every object placed in the context to en [...]
+
 ## More Information
 
 For more information about the Apache Velocity Project, see