crass package vulnerabilities
Advisories affecting the crass package. A list cannot tell you whether your installed version is affected — the dependency check can.
4 vulnerabilities tracked.
Check which version you are running → — this page lists advisories for the package; only a version check can tell you whether you are affected.
- 6.3 Crass: Non-ASCII characters cause superlinear CPU consumption
- 6.3 Crass: A large number of adjacent CSS comments can trigger a SystemStackError
- 6.3 Crass: Deeply nested CSS blocks and functions can trigger a SystemStackError or excessive memory usage
- 5.3 Crass: Incorrect tokenization of bad URLs enables CSS sanitizer bypass
What this covers
This feed accumulates forward from the day it started storing records, and a name search that finds nothing here is also looked up against the registers directly — so an older advisory resolves even when it predates the corpus. It is still a reading view, not a substitute for the vendor's own advisory, and absence from this page is not a statement that crass is free of vulnerabilities.
Query this from an agent over MCP · Check a lockfile by version
Other packages tracked here
filelock node-forge github.com/labstack/echo/v5 vllm github.com/labstack/echo/v4 undici virtualenv adminneo-org/adminneo authlib @highcharts/dashboards pypdf GitPython highcharts seroval org.keycloak:keycloak-services zip org.mariadb.jdbc:mariadb-java-client @highcharts/grid-pro russh mlflow rustls pyasn1 better-auth onnx