VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.jenkins-ci.plugins:google-login: vulnerability history, versions and safety

org.jenkins-ci.plugins:google-login is a package in the Maven ecosystem. Vulert records 5 vulnerabilities for it across 10 releases, from May 2022 to Sep 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded H1 M4
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.

See all org.jenkins-ci.plugins:google-login vulnerabilities

Vulert verdict on org.jenkins-ci.plugins:google-login 109.v022b_cf87b_e5b_ i

Updated on 23 Oct 2026

Good news: 109.v022b_cf87b_e5b_, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 5.

Package health score 66/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Quiet

What to do: Stay on 109.v022b_cf87b_e5b_ or newer. This can change: a vulnerability disclosed tomorrow can affect 109.v022b_cf87b_e5b_ too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 109.v022b_cf87b_e5b_ — unaffected i
  • Vulnerabilities on record 5 over 1 year · 0 in the last year i
  • Latest disclosure 06 Sep 2023 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 81 i
  • Last release 32 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by Maven Central, refreshed 23 Oct 2026. Licence information is not legal advice.

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

Every version Vulert tracks for org.jenkins-ci.plugins:google-login, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
1.7 13 Feb 2024 H1 MIT Yes Details →
1.1 13 Feb 2024 H1 M3 MIT Yes Details →
1.4 13 Feb 2024 H1 M1 MIT Yes Details →
109.v022b_cf87b_e5b_ 13 Feb 2024 none MIT — Details →
1.0 13 Feb 2024 H1 M3 MIT Yes Details →
1.3 13 Feb 2024 H1 M2 MIT Yes Details →
1.5 13 Feb 2024 H1 M1 MIT Yes Details →
1.2.1 13 Feb 2024 H1 M2 MIT Yes Details →
1.6 13 Feb 2024 H1 M1 MIT Yes Details →
1.3.1 13 Feb 2024 H1 MIT Yes Details →
1.2 13 Feb 2024 H1 M2 MIT Yes Details →
1.8 13 Feb 2024 none MIT — Details →

All 12 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 4
  • 2023 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 5 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for org.jenkins-ci.plugins:google-login

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-41936: Jenkins Google Login Plugin non-constant time token comparison 7.5 high 1.8 06 Sep 2023
CVE-2015-5298: Jenkins Google Login Plugin - Client-side Request Modification 6.5 medium 1.2 08 Jul 2022
CVE-2018-1000173: Jenkins Google Login Plugin Session Fixation vulnerability 5.9 medium 1.3.1 14 May 2022
CVE-2018-1000174: Jenkins Google Login Plugin Open Redirect vulnerability 5.4 medium 1.3.1 14 May 2022
CVE-2022-46683: Jenkins Google Login Plugin Open Redirect vulnerability 5.4 medium 1.7 12 Dec 2022

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.jenkins-ci.plugins:google-login

Is org.jenkins-ci.plugins:google-login safe to use?

Vulert records 5 vulnerabilities for org.jenkins-ci.plugins:google-login in Maven: 0 critical, 1 high, 4 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is org.jenkins-ci.plugins:google-login's Vulert package health score?

Vulert scores org.jenkins-ci.plugins:google-login 66/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of org.jenkins-ci.plugins:google-login affected?

No. 109.v022b_cf87b_e5b_, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of org.jenkins-ci.plugins:google-login should I use?

109.v022b_cf87b_e5b_ is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does org.jenkins-ci.plugins:google-login have?

5 vulnerabilities are recorded for org.jenkins-ci.plugins:google-login in the Maven ecosystem: 0 critical, 1 high, 4 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.jenkins-ci.plugins:google-login vulnerabilities disclosed?

0 vulnerabilities were recorded for org.jenkins-ci.plugins:google-login in the last 12 months, and the oldest entry in this database dates to 14 May 2022. 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.jenkins-ci.plugins:google-login 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.jenkins-ci.plugins:google-login for upcoming vulnerabilities?

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