LiveActive security incident?Get immediate response
CVE Record

CVE-2025-66698: An issue in Semantic machines v5.4.8 allows attackers to bypass authentication via sending a crafted HTTP r...

An issue in Semantic machines v5.4.8 allows attackers to bypass authentication via sending a crafted HTTP request to various API endpoints.

HighCVSS 8.6Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-66698 is reported as an authentication bypass in Semantic machines v5.4.8. An unauthenticated attacker could reach protected API endpoints and expose confidential data. The record names no vendor, CPE, patch, or operational workaround, so exposure must be confirmed from asset inventory and vendor guidance.

Executive priority

Treat as high priority if Semantic machines v5.4.8 is present, especially if APIs are internet-facing or handle sensitive data. The main business risk is unauthorized data exposure, but current evidence is incomplete.

Technical view

The CVE describes CWE-287 improper authentication affecting Semantic machines v5.4.8. CVSS 3.1 is 8.6: network attack vector, low complexity, no privileges, no user interaction, changed scope, and high confidentiality impact with no stated integrity or availability impact.

Likely exposure

Likely limited to environments running Semantic machines v5.4.8 with reachable API endpoints. The source bundle does not provide CPEs, vendor identity, deployment model, or affected endpoint inventory.

Exploitation context

The provided data does not support active exploitation. The CVE is not listed as KEV in the bundle. A public GitHub reference is listed, but the bundle does not establish in-the-wild exploitation or vendor confirmation.

Researcher notes

The record is sparse: affected vendor/product fields are n/a, and only the description names Semantic machines v5.4.8. Avoid broad product assumptions. Track CVE updates, GitHub reference changes, and any later vendor advisory before asserting exact scope or remediation.

Mitigation direction

  • Identify any Semantic machines v5.4.8 deployments and owners.
  • Restrict external access to related API endpoints where possible.
  • Review vendor or project guidance for patches or configuration changes.
  • Increase logging and alerting for unauthenticated API access attempts.
  • Prioritize compensating controls until an authoritative fix is confirmed.

Validation and detection

  • Search asset inventory for Semantic machines v5.4.8.
  • Confirm whether affected API endpoints are internet reachable.
  • Review authentication logs for unexpected unauthenticated API activity.
  • Check the CVE and project reference for updated vendor details.
  • Document uncertainty where product identity or fix status remains unconfirmed.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-287: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-66698 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.6CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N3.94CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

8.6High
CVSS 3.1 vector shape for CVE-2025-66698Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-287 · source CWE mapping

Improper Authentication

Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.