chore(findings): opensource/owasp-zap/owasp-zap-stable

Summary

opensource/owasp-zap/owasp-zap-stable has 2 new findings discovered during continuous monitoring.

More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/owasp-zap/owasp-zap-stable&tag=v2.16.1&branch=master

EPSS (Exploit Prediction Scoring System) provides an estimate of the likelihood that a vulnerability will be exploited in the wild.

KEV (Known Exploited Vulnerabilities) indicates whether a vulnerability is actively being exploited according to CISA.

id	source	severity	package	impact	workaround	epss_score	kev
CVE-2025-13601	Twistlock CVE	Low	glib2.0-2.84.4-3~deb13u1			N/A	false
CVE-2025-13601	Anchore CVE	High	libglib2.0-0t64-2.84.4-3~deb13u1			N/A	false

More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/owasp-zap/owasp-zap-stable&tag=v2.16.1&branch=master

Novel Tidelift Findings (Experimental)

opensource/owasp-zap/owasp-zap-stable has 4 novel Tidelift findings discovered during continuous monitoring.

NOTE: This table is for Iron Bank evaluation and testing purposes. No action required by vendors.

id	cvss score	package	impact	workaround	epss_score	kev
CVE-2025-46392	2.7	commons-configuration:commons-configuration-1.10			0.00122	false
CVE-2025-48924	6.5	commons-lang:commons-lang-2.6			0.00070	false
CVE-2025-48924	6.5	org.apache.commons:commons-lang3-3.17.0	An application or library would need to not only use the API or one of its call sites but also allow for very long inputs for a class name. Alternatively, if the app or library accepts input from the user or a configuration file, the app stack may be vulnerable.		0.00070	false
CVE-2025-48734	8.8	commons-beanutils:commons-beanutils-1.10.1	An application or library can be vulnerable if it allows inputs or configurations from untrusted sources.		0.00059	false

Tasks

Contributor:

• Apply the StatusReview label to this issue for a merge request review and wait for feedback

OR

• Provide justifications for findings in the VAT (docs)
• Apply the StatusVerification label to this issue for a VAT justifications review and wait for feedback

Iron Bank:

• Review findings and justifications

Note: If the above process is rejected for any reason, the Review or Verification label will be removed and the issue will be sent back to To-Do. Any comments will be listed in this issue for you to address. Once they have been addressed, you must re-add the Review or Verification label.

Questions?

Contact the Iron Bank team by commenting on this issue with your questions or concerns. If you do not receive a response, add /cc @ironbank-notifications/onboarding.

Additionally, Iron Bank hosts an AMA working session every Wednesday from 1630-1730EST to answer questions.