I have not looked through all of the documents, but I am familiar with some of them. I am also a cyber security expert (with forensic investigation certification, and information security certifications) So far, I have not seen anything that hasn't been "public knowledge"* for a long time. These were not secrets.. not by a longshot.
* the public is not very knowledgeable of cyber security... that is why 1 out of 12 people click ridiculously suspicious links, because of ignorance. (according to the Verizon data breach report in 2016).
I can understand why people think these are some kind of "secret CIA toolkit" that no one is supposed to know about... because basically, not many pople choose to educate themselves about it.
"The Internet of Things" has been a topic of concern in my industry for years... Google "Internet of things security". smart TVs have had known, and publically released information about vulnerabilities for YEARS.
People don't care. They just want to plug in their new toy and it just work with minimal effort... no setting of passwords, no configuring of firewalls...
People are willfully ignorant of all the technological vulnerabilities that exist. In all fairness, the issues are complex. But the solution is simple... install the vendor supplied patch and set a password that is at least slightly better than completely stupid to use.
Cyber Security experts often will find a vulnerability in some software (or firmware, if an embedded device), contact the vendor about it, and then nothing happens. More recently, the industry has taken a more draconian approach to getting vendors to clean up the mess they make... security experts will disclose a vulnerability they found to the vendor, then give them 30 days to fix it (even if temporarily before a final fix can be made), and if they fail to acknowledge the flaw or fix it in 30 days, the information about the vulnerability is dumped on the internet for all to see.
Many cyber security experts would say that public disclosure of vendor weaknesses in technology is the RIGHT think to do. It is what compels companies that have sloppy development practices to clean up their act, in the name of personal, and even national, security.
Microsoft was a great example. Companies burn MILLIONS of dollars every year just trying to keep up with MS's constant security patches. "Patch Tuesday" is a thing. The first Tuesday of every month represents a release of a slew of all new security flaws and fixes for Microsoft products. It took DECADES before anything was done to fix Microsoft's practice of pushing out insecure and poorly developed software, just to make customers fix it every month.
Publish it, shame the vendor, and demand fixes.