Vulnerability Database · Maven · Package report

org.thymeleaf.examples:thymeleaf-examples-springsecurity5: vulnerability history, versions and safety

org.thymeleaf.examples:thymeleaf-examples-springsecurity5 is a package in the Maven ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Maven ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on org.thymeleaf.examples:thymeleaf-examples-springsecurity5 i

Updated on 23 Oct 2026

Good news: Vulert has no vulnerability on record for org.thymeleaf.examples:thymeleaf-examples-springsecurity5 in the Maven ecosystem. That is a good sign, not a guarantee — keep an eye on the versions you run.

Long-term outlook: healthy with no vulnerability recorded so far.

What to do: Run a supported release and keep monitoring: new vulnerabilities are published for packages every day. Nothing yet: a new vulnerability can appear at any time — Vulert alerts you if one affects this package. Monitor it with Vulert →

  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

No version data is recorded for this package yet.

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for org.thymeleaf.examples:thymeleaf-examples-springsecurity5

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About org.thymeleaf.examples:thymeleaf-examples-springsecurity5

Is org.thymeleaf.examples:thymeleaf-examples-springsecurity5 safe to use?

Vulert has no vulnerabilities on record for org.thymeleaf.examples:thymeleaf-examples-springsecurity5 in Maven at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

How many vulnerabilities does org.thymeleaf.examples:thymeleaf-examples-springsecurity5 have?

0 vulnerabilities are recorded for org.thymeleaf.examples:thymeleaf-examples-springsecurity5 in the Maven ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.thymeleaf.examples:thymeleaf-examples-springsecurity5 vulnerabilities disclosed?

0 vulnerabilities were recorded for org.thymeleaf.examples:thymeleaf-examples-springsecurity5 in the last 12 months. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of org.thymeleaf.examples:thymeleaf-examples-springsecurity5 are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor org.thymeleaf.examples:thymeleaf-examples-springsecurity5 for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the org.thymeleaf.examples:thymeleaf-examples-springsecurity5 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.