Skip to content

← Actionable
High, CVSS 8.1

OpenDaylight SFC Insecure Shiro Cookie Configuration

CVE-2025-29314GHSA-xp75-w7vq-5x6j

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • Maven org.opendaylight.sfc:odl-sfc-ovs

    Affected
    <= 0.10.4
    Fixed in
    no fixed version recorded
  • Maven org.opendaylight.sfc:odl-sfc-openflow-renderer

    Affected
    <= 0.10.4
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.1 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2025-29314: 0.22% estimated exploitation activity in the next 30 days; percentile 12.72 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Insecure Shiro cookie configurations in OpenDaylight Service Function Chaining (SFC) Subproject SFC Sodium-SR4 and below allow attackers to access sensitive information via a man-in-the-middle attack.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-xp75-w7vq-5x6j

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-29314

Advisory: OpenDaylight SFC Insecure Shiro Cookie Configuration
IDs: CVE-2025-29314, GHSA-xp75-w7vq-5x6j
Record: https://patchnext.com/advisories/cve-2025-29314 (revision 1, source checked 26 Oct 2026, 16:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.opendaylight.sfc:odl-sfc-ovs: affected <= 0.10.4
- Maven org.opendaylight.sfc:odl-sfc-openflow-renderer: affected <= 0.10.4

## Suggested inspection (read-only)
- Maven org.opendaylight.sfc:odl-sfc-ovs: check the installed version with your package manager.
- Maven org.opendaylight.sfc:odl-sfc-openflow-renderer: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.opendaylight.sfc:odl-sfc-ovs, org.opendaylight.sfc:odl-sfc-openflow-renderer.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-xp75-w7vq-5x6j (GitHub-reviewed advisory GHSA-xp75-w7vq-5x6j lists affected ranges: Maven org.opendaylight.sfc:odl-sfc-ovs >=0 =0 <=0.10.4)

Commands are suggestions: review each one before running it.

Loading voting…