With the required third party fix, you now effectively have a precondition for your story (that you assumed would be present from the start, but it turned out it wasn't).
You should put the story back into the backlog at the end of the sprint. It's not done. Whether you put it into a next sprint depends on your team's rules, but I would not do it unless the precondition is checked and validated before the start of the sprint.
A sprint should be filled with items so that the team thinks it can deliver that amount at the end of the sprint. If it's unclear whether a precondition can be fulfilled during the sprint, it should not even be a topic in the planning meeting, other than saying "preconditions not available? Okay, NEXT". A sprint should only be filled with items the team can deliver.
As always, exceptions may apply. A new backlog item for the next sprint might be "check out if the bug is still not fixed in their 1.2.3 release that comes out on tuesday". That can be done, even though the "done" result of the story might be "it's still buggy, we cannot proceed with the original story next sprint".