anshumg commented on PR #261: URL: https://github.com/apache/solr-site/pull/261#issuecomment-7017224175
Hey @epugh , I'd push back on a blanket VEX for Solr, because I don't think it's the right tool for most of what we ship. CVE-2026-114938 lives in the JVM, not in Solr. For the binary/.tgz distribution we bundle no JDK, so there's no Solr artifact for a scanner to match and no SBOM node to attach a statement to - "update your runtime" is the whole story. If we commit to publishing VEX for runtime CVEs across the project, the same logic pulls us into issuing statements for every JDK, kernel, libc, and TLS CVE on every platform Solr runs on. That's an unbounded commitment I don't think we want to take on by default. The one place it genuinely fits is the Docker images - those bundle a JDK (an affected one), so a scanner will match this against the image SBOM. So rather than VEX-for-everything, I'd suggest: a security advisory for the project as a whole, plus a fixed VEX scoped specifically to the image. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
