CVE-2026-120447

waiting for further signalsZero needs more public information before it can validate it.

GHSA-c3f7-678j-f69g ↗EUVD-2026-115207 ↗

no check availablenot proven exploitable
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.
bufanyun HotGo <= 2.15.1
ETK-2026-3297Zero's internal tracking ID, independent of the CVE number., permanent identifier
4h 25msince last run
44mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+2h39m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

HotGo through version 2.15.1 is affected by an authentication bypass in its SMS-based login flow. An unauthenticated attacker who knows a target user's mobile number may be able to take over that account, including an administrator account.

mitigation

Restrict public access to the affected SMS login and administration endpoints until an upstream update or verified vendor fix is available. Limit access to trusted networks and monitor for unexpected SMS-login activity.

check
no
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.
contextual
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.
–
agent run time
44m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-02 14:29Z
Δ 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.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-02 14:29Z
    ghsa: trigger signal, started the run
  2. 2026-11-02 14:29Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3297",
  "cve_id": "CVE-2026-120447",
  "display_id": "CVE-2026-120447",
  "ghsa_id": "GHSA-c3f7-678j-f69g",
  "euvd_id": "EUVD-2026-115207",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authentication bypass in bufanyun HotGo SMS login",
  "summary": "HotGo through version 2.15.1 is affected by an authentication bypass in its SMS-based login flow. An unauthenticated attacker who knows a target user's mobile number may be able to take over that account, including an administrator account.",
  "mitigation": "Restrict public access to the affected SMS login and administration endpoints until an upstream update or verified vendor fix is available. Limit access to trusted networks and monitor for unexpected SMS-login activity.",
  "vendor": "bufanyun",
  "product": "HotGo",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 2.15.1"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "HotGo",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 44.37110318333333,
  "t0_at": "2026-11-02T14:29:06.746000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-02T14:29:06.746000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-02T14:29:06.746000+00:00",
      "url": "https://github.com/advisories/GHSA-c3f7-678j-f69g"
    }
  }
}

published 2026-11-02 16:23Z
last change 2026-11-02 19:32Z

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.