Authenticated crash or stack disclosure via Redis format
Published Aug 19, 2026 · Updated Aug 20, 2026
Format string injection in coturn before 4.13.0 allows remote authenticated users to crash the server via crafted STUN USERNAME or REALM values. is_secure_string() in src/apps/common/ns_turn_utils.c accepts '%' characters, src/apps/relay/ns_ioalib_engine_impl.c copies the resulting USERNAME or REALM into Redis keys, and send_message_to_redis() in src/apps/relay/hiredis_libevent2.c passes that key to redisAsyncCommand() as the format string while supplying only one data argument. Reachability is limited to deployments with hiredis integration and valid TURN credentials; exploitation can terminate active TURN sessions and can write stack-derived data into Redis, but the public record does not show a reliable integrity impact.
Summary
What happened
Format string injection in coturn before 4.13.0 allows remote authenticated users to crash the server via crafted STUN USERNAME or REALM values. is_secure_string() in src/apps/common/ns_turn_utils.c accepts '%' characters, src/apps/relay/ns_ioalib_engine_impl.c copies the resulting USERNAME or REALM into Redis keys, and send_message_to_redis() in src/apps/relay/hiredis_libevent2.c passes that key to redisAsyncCommand() as the format string while supplying only one data argument. Reachability is limited to deployments with hiredis integration and valid TURN credentials; exploitation can terminate active TURN sessions and can write stack-derived data into Redis, but the public record does not show a reliable integrity impact.
The record
- CVE
- CVE-2026-68553
- Published
- Aug 19, 2026
- Updated
- Aug 20, 2026
- Vendor
- coturn
- Product
- coturn
- Classifications
- CWE-134, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 19, 2026CVE publishedPublication date reported by the CVE source.
- Aug 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.13.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo