dbcve.org
Gridtime 3000 FirmwareOperating system · Microchip

CVE-2026-12620

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-19
Fix available
A fix is available. Upgrade to 1.2r0.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The GridTime 3000 GNSS Time Server leaks the access token in the URL parameters of some endpoints. This issue affects GridTime 3000: from 1.0r0.03 through 1.1r0.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The GridTime 3000 GNSS Time Server improperly exposes access tokens in URL query parameters on certain endpoints. This allows tokens to be captured via server access logs, browser history, proxy logs, or network interception, enabling session hijacking or unauthorized access.

MitigationMigrate authentication from URL parameters to secure methods (Authorization headers or secure cookies). Until patched, monitor server logs for exposed tokens and consider rotating potentially compromised credentials.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Gridtime 3000 FirmwareOperating system
Affected:>= 1.0r0.03, < 1.2r0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed firmware version
    Access the device web interface or CLI and locate the firmware version information, typically found in System > About or via 'show version' command
    Affected if version is >= 1.0r0.03 and < 1.2r0.0
  2. Identify authentication endpoints using URL parameters
    Review application or API documentation, or inspect browser developer tools/network traces when logging in to observe if authentication tokens appear in the URL query string (e.g., ?token=xxx or ?auth=xxx)
    Affected if tokens or session identifiers are transmitted via URL query parameters rather than headers or cookies
  3. Examine server access logs for token leakage
    Locate and search web server logs, proxy logs, or WAF logs for patterns containing 'token=', 'auth=', or 'sessionid=' in URL query strings
    Affected if logs contain entries with sensitive tokens exposed in URLs

You are affected if your GridTime 3000 firmware version falls within 1.0r0.03 through 1.2r0.0 and your logs or network traffic show authentication tokens being passed in URL query parameters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.2r0.0 or later
Fixed in 1.2r0.0
Interim mitigation

Migrate authentication from URL parameters to secure methods (Authorization headers or secure cookies). Until patched, monitor server logs for exposed tokens and consider rotating potentially compromised credentials.

Recommended fix Moderate confidence

Firmware version 1.2r0.0 or later

  1. 1. Identify the current firmware version of the GridTime 3000 device by accessing the device web interface or checking system information.
  2. 2. Navigate to the Microchip support website (www.microchip.com) and locate the GridTime 3000 firmware downloads section.
  3. 3. Download firmware version 1.2r0.0 or later, ensuring it is the appropriate variant for your specific GridTime 3000 model.
  4. 4. Review the firmware upgrade instructions provided by Microchip in the release notes or user documentation.
  5. 5. Perform the firmware upgrade following the manufacturer's recommended procedure, typically via the device's web-based management interface or dedicated upgrade tool.
  6. 6. After completing the upgrade, verify that the device is running firmware version 1.2r0.0 or later.
  7. 7. Test the affected endpoints to confirm that access tokens are no longer exposed in URL parameters.
Caveat Review Microchip release notes for any configuration or feature changes between 1.1r0.0 and 1.2r0.0; firmware upgrades on time servers may require reconfiguration of network and time synchronization settings

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gridtime 3000 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-12620 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-12620 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data