Show us your code. This code works fine:

package main

import "math"

func main() {
	var x uint = math.MaxUint64
	_ = x
}

The definition of MaxUint64 as 1<<64-1 has no issues with overflow. It is a constant expression, which in Go is evaluated with arbitrary precision/range.

Show us your code. This code works fine:

package main

import "math"

func main() {
	var x uint = math.MaxUint64
	_ = x
}

The definition of MaxUint64 as 1<<64-1 has no issues with overflow. It is a constant expression, which in Go is evaluated with arbitrary precision/range.

Your code works well.
Here is my code.

package main

import "math"
func main() {
 	x := math.MaxUint64
	_ = x
 }

Is this related to untyped constant? The untyped constant math.MaxUint64 cannot infer the type from x that has no type. So it is given the default type int, so it overflows.

Yes, the second example is due to the type inference with the untyped constant.

x := math.MaxUint64

infers that x is an int and it overflows.

Also, the first example

var x uint = math.MaxUint64

still overflows on any architecture where uint is 32-bit, e.g. arm.

If you want to assign math.MaxUint64 to a variable you need to store it in a uint64

Closing, this is working as intended.
As @bmkessler says, explicitly type your variable instead of using :=.

See also #19621, #23086, #23087, #23163.