Latest

Cybersecurity

FreeSWITCH and Apache Juneau hit by severe flaws affecting both projects

The open source phone switch publishes a flaw with a public proof of concept, and Apache Juneau racks up five critical ones in the same week.

FreeSWITCH and Apache Juneau release a 9.8 and five 10.0s
FreeSWITCH and Apache Juneau release a 9.8 and five 10.0s

FreeSWITCH, the open source phone switch that carriers and enterprises use to run their own voice service, published an advisory for a vulnerability scored 9.8 out of 10 with a public proof of concept. Apache Juneau, a serialization framework that almost nobody installs on purpose, racked up five separate vulnerabilities scored the maximum 10 in the same week.

Both stories appeared on November 5 in the CiberLab security newsletterwhich that day collected 202 alerts in a single session and serve to illustrate two distinct problems. The first is that public proof of concept changes the urgency of a flaw even if the score does not move. The second is that a score of 10 does not distinguish between a deep logic error and a poorly filtered header, and that difference should matter more than the industry admits.

Neither case has confirmed victims, so the useful reading is not the press headline but that of the administrator who has to decide this week what to patch first and what can wait until Friday without taking on a risk they did not choose. Exposure first, urgency second.

FreeSWITCH 9.8 and the sign that triggers it

The flaw is tracked as CVE-2026-116779 and affects versions prior to 1.11.3. The cause lies in the `sofia_presence_handle_sip_i_message()` function, which processes incoming SIP messages and splits the recipient's user from the domain at the plus sign to interpret the left-hand part as a number and the right-hand part as a domain.

Validation of that split is insufficient, so a carefully crafted request gets the server to execute code in the context of the process. The 9.8 score reflects that no authentication is required and that the attacker only needs to reach the SIP port, which on a phone system exposed to the internet is the default configuration.

Version 1.11.3 fixes the problem. What raises the urgency above average is that the proof of concept is public, and a public demonstration turns a theoretical flaw into a tool anyone can run within hours. The project FreeSWITCH keeps the fixed versions in its official repository.

Five 10.0s in Apache Juneau

The Apache Juneau case is stranger. The project accumulated five vulnerabilities with a score of 10 on the same day: script execution in HTML serialization, a newline in headers that allows an HTTP response to be split, credentials that survive a redirect, an error message that exposes the internal exception and a log that stores headers without redacting them.

The identifiers are CVE-2026-96677 for the script execution, CVE-2026-73117 for the newline, CVE-2026-73116 for the credentials on redirect, CVE-2026-73101 for the error message and CVE-2026-73100 for the log. All share one characteristic, which is that they stem from treating request data as if it were trusted. The advisories are published in the Apache security tracking.

The headers

The score of 10 in all five cases is explained by the fact that the vector is network, the complexity is low and no authentication is required. What it does not explain is the real impact, which depends on whether the component is exposed, what data it handles and whether anyone uses it in production.

The most interesting group is the headers. In case 73117, the server passes response values and redirect destinations to the container without checking them, which allows line breaks to be inserted and custom headers to be added. In 73116, the client follows redirects while retaining the credential headers from the original request, so a server that redirects to another host receives an `Authorization` that does not belong to it.

73101 and 73100 are information leaks through channels that are often overlooked. The first sends the class and message of the internal exception in a header of every error response, and the second logs the headers of requests that end in error without redacting credentials. None of the four is a cryptography or memory management flaw; they are errors of judgment about what is considered secure by default.

SuiteCRM and the SSRF in the test button

The day's newsletter also included a high-severity flaw in SuiteCRM, a customer management system widely used by mid-sized companies. Vulnerability CVE-2026-69137 has a score of 7.7 and affects versions prior to 7.15.2 and 8.10.2.

The problem lies in the `testConnection` action of the calendar accounts module, which passes the URL supplied by the caller directly to the download tool without validating the host, address or scheme. An authenticated user can use that function to make the server send requests to internal addresses, which in practice opens up the company's private network from a form.

It is the kind of flaw that draws no attention and yet does appear in real investigations, because it serves to identify what is behind the firewall before a larger attack.

The score is not the priority

The first question is not the score, it is exposure. A FreeSWITCH with the SIP port open to the internet is this week's problem; an Apache Juneau embedded in an internal library with no network access is a task for the next maintenance window. The second is whether there is a proof of concept, because a public demonstration reduces the available time to days and an observed exploitation reduces it to hours.

The coincidence of five 10.0s in the same project should feed a discussion about how these things are scored. A system that assigns the maximum to an unfiltered header and to a remote code execution stops being useful for prioritizing work, and the analysis of how to triage an avalanche of CVEs already warned that the score alone does not order an inventory.

For the administrator, the practical consequence is that the score serves as an initial filter and never as a final criterion. Exposure, proof of concept and reachable data decide the real order, and no vulnerability database performs that calculation. The methodology for doing so without losing your mind is in the guide on how to read a CVE if it affects you, and the case of the compression library that took down half of Node.js illustrates it in Node2Shell.

José Maldonado

Author

José Maldonado

Activist and blogger on technology, free software and blockchain.

The latest
From Huang to Botín, from Zara to Byron: corporate responsibility in global capitalism

Keep reading