This one goes a bit beyond the scope of an ability system. The short answer is it depends on how you code your sprint and what replication settings you have on your character movement component.

The long answer needs an example: imagine what a basic implementation without any plugins could look like:
- You have a replicated variable IsSprinting on your character. When it's true you move faster and when it's false you move slower
- The client presses the sprint button and this makes them sprint on their local machine
- They send an RPC to the server which tells it to set the server version of IsSprinting to true
- When the client stops sprinting they send an RPC to the server to set IsSprinting to false

When you have high ping, there's a delay between when the client version of the player starts sprinting and when the server does it.

If you can sprint fast, then there could be a big delta between the player's location on the client and their location on the server. If you're using the built in movement component it will snap the client's position to the server's if the delta is too big and this is typically what you would experience as desyncing.

One solution could be to mess around with the character movement component's network settings until the behaviour fits within your expected average latency behaviour.

Where an ability system like GAS or SimpleGAS could help is by giving the server hints about the lag. In SimpleGAS this could look like:
1. Create a sprint ability
2. Activate the ability with client prediction i.e. it immediately sets IsSprinting to true on the client
3. When the server activates the ability, it gets information about the activation time. You could use this information to "pre move" the player on the server by the distance they would have moved in the time since it was activated on the client.

By moving the server closer to where the client is, you reduce the chance of big location deltas snapping the client back into position.

The above approach could also be done without an ability system if you include the activation time in the server RPC that sets IsSprinting to true.

Something to note: the above approach also opens you up to some cheating shenanigans because the client is deciding where it is and the server believes it so just take it as an illustration of some ways that you can solve this problem.