Signal Vindicated: Denver Experts Spotlight Human Error in Chat Leak
Summary
- Human Error, Not Hacking: Two Denver cybersecurity experts say the leak of a government Signal group chat came from a person being added by mistake.
- Signal Itself Held Up: Neither expert saw any sign that Signal’s encryption was compromised.
- Experts Weigh In: A University of Denver cybersecurity professor and a Denver encrypted-messaging startup founder spoke to Denver7.
- Broader Implications: Secure tools still depend on how people use them.
What the Denver Experts Said
The March 2025 leak of a Signal group chat among senior Trump administration officials led some critics to question the encrypted messaging app itself. A journalist from The Atlantic had been added to the chat by mistake. Two Denver cybersecurity experts told Denver7 that Signal was not to blame.
Why Experts Trust Signal
Nathan Evans is a teaching associate professor and faculty director for cybersecurity programs at the University of Denver’s Ritchie School of Engineering and Computer Science. He has worked in cybersecurity for nearly 20 years and said Signal is well respected in the field.
“It’s created by a very well-respected cybersecurity researcher, and that brings a lot to the game,” Evans said. “If somebody on the street was going to say, ‘What should I use for encrypted messaging?’ I would probably say Signal’s your best bet.”
Start your morning with the signal that matters.
Weekday mornings. Five minutes. What changed in security, why it matters.
By subscribing you agree to our Privacy Policy.
Free. Weekday mornings. 5 minutes or less.
A Mistake in Who Got Access
Evans believes the leak came down to human error. Someone was given access to a group chat they should never have been in. The app did what it was built to do.
“It’s not that Signal was compromised or that Signal has security issues,” he said. “It’s just that people were using something when they weren’t supposed to, and it was really just a mistake of giving somebody access to the group messages that wasn’t supposed to have access to it.”
A Startup Founder’s View
Tanner Haas, a Denver entrepreneur and founder and CEO of Freedom Chat, a new encrypted messaging app, agreed. “It has nothing to do with their encryption,” Haas said. “The encryption is sound.”
Haas said Freedom Chat would add a feature in response to the leak. In a chat marked top secret, adding a new member would require approval from every other member of the group, a guard against someone being added by accident.
The Policy Question
Democrats pointed out that Signal is not approved for sensitive military intelligence. The Trump administration argued the conversations did not contain sensitive information.
Start your morning with the signal that matters.
Weekday mornings. Five minutes. What changed in security, why it matters.
By subscribing you agree to our Privacy Policy.
Free. Weekday mornings. 5 minutes or less.
Most people agree the journalist should never have been in the chat.
For organizations, the lesson is practical: strong encryption protects messages in transit, but it can’t stop users from inviting the wrong person. Clear rules about which tools are approved for sensitive work, and checks on who gets added to group chats, matter as much as the technology.
Newer CyberExperts coverage on this topic
This article still works as background. If you want the current picture, start with the freshest related coverage below and today's brief.
Citrix NetScaler CVE-2026-19490: The Auth Bypass That Went From PoC to Probes in a Day
CVE-2026-19490 is a CVSS 9.3 NetScaler Gateway/AAA auth bypass. A public PoC on Sept 2 was followed by live probes within a...
PaperCut NG/MF: The Print Server That Learned Remote Code Execution Again
CVE-2026-81578 and CVE-2026-82078 chain to pre-auth RCE on PaperCut Application Server. Confirm Emergency Patch Release 2, restrict admin exposure, and hunt like...
JFrog Artifactory CVE-2026-82329: Empty Join Key, Full Admin Token, Busy Scanners
CVE-2026-82329 lets attackers forge Artifactory admin tokens via a deterministic empty join key. Mass scanning peaked near 406,000 attempts; patch fixed builds...
Friday’s brief: Apache’s HTTP/2 fix, then Check Point break-ins, a ScreenConnect add-on and a GitHub secret stealer
The fastest way to catch up on what changed after this article was published.
Start your morning with the signal that matters.
Get the biggest cybersecurity developments, why they matter, and where to go deeper on CyberExperts.
By subscribing you agree to our Privacy Policy.
Free. Weekdays. Built for operators.