gotenbergpackaged by Chainguard
packaged by Chainguard
Last changed
Request a free trial
Contact our team to test out this image for free. Please also indicate any other images you would like to evaluate.
Tag:
Severity:All
Expand | CVE ID | Severity | Package | Version | Last detected |
|---|---|---|---|---|---|
CVE-2026-95325 | Critical | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95356 | Critical | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95349 | Critical | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95310 | Critical | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95350 | Critical | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95283 | Critical | chromium | 153.0.8010.52-r2 | ||
CVE-2026-102306 | Critical | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95299 | Critical | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95313 | Critical | chromium | 153.0.8010.52-r2 | ||
CVE-2026-102308 | Critical | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95339 | Critical | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95347 | Critical | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95357 | Critical | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95281 | Critical | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95277 | Critical | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95331 | Critical | chromium | 153.0.8010.52-r2 | ||
CVE-2026-102304 | Critical | chromium | 153.0.8010.52-r2 | ||
CVE-2026-102331 | Critical | chromium | 153.0.8010.52-r2 | ||
CVE-2026-102309 | Critical | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95318 | Critical | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95284 | Critical | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95311 | Critical | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95329 | Critical | chromium | 153.0.8010.52-r2 | ||
CVE-2026-102316 | Critical | chromium | 153.0.8010.52-r2 | ||
CVE-2026-102321 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95343 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95345 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95333 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95319 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-102324 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95306 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95280 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95285 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95322 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95351 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-102328 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95278 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95282 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95341 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95338 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-102301 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-102327 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95274 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95348 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95326 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95298 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95376 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95314 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95354 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95304 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-102302 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95380 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95335 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-102323 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95301 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95372 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95315 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95276 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95286 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95373 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95365 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95369 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-102299 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95344 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95362 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-102326 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95381 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95353 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95334 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95355 | High | chromium | 153.0.8010.52-r2 | ||
CVE-2026-102303 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-102329 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95294 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95370 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-89092 | Medium | glibc-2.44 | 2.44-r7 | ||
CVE-2026-95300 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-15534 | Medium | perl | 5.44.0-r1 | ||
CVE-2026-95384 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-102310 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95352 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-90781 | Medium | alsa-lib | 1.2.16.1-r2 | ||
CVE-2026-95297 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95309 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95307 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95367 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95321 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95279 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-102330 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95291 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95363 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95342 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95296 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95305 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95287 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95346 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-8674 | Medium | glibc-2.44 | 2.44-r7 | ||
CVE-2026-102312 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-102307 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95361 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-96675 | Medium | alsa-lib | 1.2.16.1-r2 | ||
CVE-2026-95328 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95375 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95368 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95293 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95288 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-102320 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-96674 | Medium | alsa-lib | 1.2.16.1-r2 | ||
CVE-2026-95358 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95289 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95327 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-102325 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-102314 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95292 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95330 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95371 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-102305 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95295 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95303 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95323 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95382 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95332 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95360 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95374 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95340 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95290 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95336 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95337 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-86805 | Medium | glibc-2.44 | 2.44-r7 | ||
CVE-2026-95275 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95366 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95320 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95364 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-102318 | Medium | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95308 | Low | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95324 | Low | chromium | 153.0.8010.52-r2 | ||
CVE-2026-102319 | Low | chromium | 153.0.8010.52-r2 | ||
CVE-2026-97399 | Low | glibc-2.44 | 2.44-r7 | ||
CVE-2026-102311 | Low | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95302 | Low | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95317 | Low | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95312 | Low | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95359 | Low | chromium | 153.0.8010.52-r2 | ||
CVE-2026-95818 | Low | glibc-2.44 | 2.44-r7 | ||
CVE-2026-95316 | Low | chromium | 153.0.8010.52-r2 | ||
GO-2026-5932 | Unknown | golang.org/x/crypto | v0.57.0 | ||
GO-2026-5932 | Unknown | golang.org/x/crypto | v0.56.0 |
Last updated:
The trusted source for open source
Talk to an expertProduct
Customers
© 2026 Chainguard, Inc. All Rights Reserved.
Chainguard® and the Chainguard logo are registered trademarks of Chainguard, Inc. in the United States and/or other countries.
The other respective trademarks mentioned on this page are owned by the respective companies and use of them does not imply any affiliation or endorsement.
Chainguard® and the Chainguard logo are registered trademarks of Chainguard, Inc. in the United States and/or other countries.
The other respective trademarks mentioned on this page are owned by the respective companies and use of them does not imply any affiliation or endorsement.