This has come up now and again over the years. The best I can guess is it’s just some fluky macOS bug. (If it were affecting everybody, and tied to a given release, that would be one thing — but it’s not.)
If you’re nervous about it, you could update manually — download the latest version from netnewswire.com.
Do you happen to have another (newer or older) copy of NetNewsWire on your computer? (My thinking is that somehow @rpath/Sparkle.framework/Versions/A/Sparkle is finding the wrong framework.)
May I ask what you did to make it work? So you found that another app (ScrummVM) included a different version of Sparkle… did you perhaps uninstall it, or update it, and then found that NetNewsWire was able to check for updates?
Did some digging in the Sparkle documentation (since ScummVM.app is using a newer version of Sparkle and discovered that this issue is most likely fixed in 2.6.4 and later of Sparkle).
The developer’s updating Sparkle usage within NetNewsWire.app is possibly going to need some thinking for the new version because NetNewsWire.app is (I think) a sandboxed app.