Skip to main content
VulnerabilityPublished Updated

CVE-2026-62253: sipcapture homer · Missing Authentication

Affects sipcapture homerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.8 Critical : upgrade to 11.0.283 as a priority.

Data as of 21 Nov 2026, 17:35 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 11.0.283
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.

What to do

Upgrade homer and sipcapture/homer to 11.0.283.

Affected software

ProductAffectedFixed in
sipcapturehomerAffected
  • <11.0.283
Fixed in
  • 11.0.283
GitHubsipcapture/homerpkg:github/sipcapture/homerOther threatsAffected
  • <11.0.283
Fixed in
  • 11.0.283

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Homer to version 11.0.283 or later, where the JWT middleware correctly enforces authentication by requiring a non-empty jwtSecret. No other mitigation is required as the issue is fixed in this official release.

Description

Homer, an open source telecom observability software, had a critical vulnerability (CVE-2026-62253) prior to version 11.0.283 where its JWT middleware functions allowed unauthenticated access to protected API endpoints. This was due to the JWT secret defaulting to an empty string, causing the middleware to bypass authentication checks. The issue was fixed in version 11.0.283.

References

Community reviews

Loading reviews…