CVE-2026-28185

validatedZero produced an exploit or a check.

GHSA-f3m5-j625-hff8 ↗EUVD-2026-57963 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.+71d
rtCamp Log in with Google >= n/a, <= 1.4.2
ETK-2026-2539Zero's internal tracking ID, independent of the CVE number., permanent identifier
+72dTTV
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
cve.org publicationtrigger signal +70dkev+71dcheck available+72dagent stopped
0
+20d
+40d
+60d
+80d

description

rtCamp Log in with Google versions through 1.4.2 are affected by an unauthenticated broken-authentication flaw. An attacker may be able to compromise authentication without prior access; the advisory provides no further preconditions or technical detail.

mitigation

Update to a vendor-supported release newer than 1.4.2 if one is available. Until an update is confirmed, disable the plugin or restrict access to the affected authentication functionality to reduce exposure.

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
deterministic
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.27%18th percentile
agent run time
<1m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-08-13 13:36Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
+71d

outcome

Upstream: a detection for this already ships elsewhere, so we didn't generate a new one. The credit goes to whoever did.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-08-13 13:36Z
  2. 2026-10-23
    vulncheck_kev: trigger signal, started the run
  3. 2026-10-23 00:00Z
  4. 2026-10-24 13:51Z

this entry in the feed

GET /api/v1/feed/CVE-2026-28185

{
  "etk_id": "ETK-2026-2539",
  "cve_id": "CVE-2026-28185",
  "display_id": "CVE-2026-28185",
  "ghsa_id": "GHSA-f3m5-j625-hff8",
  "euvd_id": "EUVD-2026-57963",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated broken authentication in rtCamp Log in with Google",
  "summary": "rtCamp Log in with Google versions through 1.4.2 are affected by an unauthenticated broken-authentication flaw. An attacker may be able to compromise authentication without prior access; the advisory provides no further preconditions or technical detail.",
  "mitigation": "Update to a vendor-supported release newer than 1.4.2 if one is available. Until an update is confirmed, disable the plugin or restrict access to the affected authentication functionality to reduce exposure.",
  "vendor": "rtCamp",
  "product": "Log in with Google",
  "affected": [
    {
      "affected_notes": [
        ">= n/a, <= 1.4.2"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "login-with-google",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.8,
  "cvss_src": "other",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0027,
  "epss_percentile": 0.1879,
  "epss_asof": "2026-10-23",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.2814958833333333,
  "t0_at": "2026-08-13T13:36:37.635000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-24T13:51:55.148502+00:00",
      "days": 72.01061936923611,
      "is_lower_bound": false,
      "measured_at": "2026-08-13T13:36:37.635000+00:00",
      "url": null
    },
    "kev": {
      "at": "2026-10-23T00:00:00+00:00",
      "days": 71,
      "is_lower_bound": false,
      "measured_at": "2026-08-13T13:36:37.635000+00:00",
      "precision": "day",
      "url": "https://vulncheck.com/cve/CVE-2026-28185"
    },
    "trigger_signal": {
      "at": "2026-10-23T00:00:00+00:00",
      "days": 70.43289774305556,
      "is_lower_bound": false,
      "measured_at": "2026-08-13T13:36:37.635000+00:00",
      "url": "https://vulncheck.com/cve/CVE-2026-28185"
    }
  }
}

published 2026-10-24 13:51Z
last change 2026-10-24 16:34Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.