> That link is not an issue with json, but with javascript (that js treats keys named __prototype__ special). JSON is meant to be (and was widely advertised as

> That link is not an issue with json, but with javascript (that js treats keys named __prototype__ special). JSON is meant to be (and was widely advertised as) a Javascript subset, but isn't, but almost no one is aware of this. So of course it's also an issue with JSON. It's also not the only divergence that leads to security problems, in fact if you follow the first link in the comment you will see that this was posted in the context of trying to fix another misspecification in an attempt to actually make JSON a proper subset (which turned out to be impossible to completely accomplish, although at least the paragraph separator issue has been fixed in 2019). See here: https://v8.dev/features/subsume-json https://v8.dev/features/subsume-json