FKIE_CVE-2026-50578

Vulnerability from fkie_nvd - Published: 2026-08-18 17:16 - Updated: 2026-08-18 18:18
Severity
7.5 (High) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Summary
ePA 3.x Integration implements the authorization workflow and writes Medical Information Objects to Germany's electronic patient record. Prior to 1.3.0, ePA 3.x Integration disables TLS certificate verification for both ePA connections in app/vau/VAUProtokoll.py and Konnektor connections in app/konnektor/Konnektor.py. A network-positioned attacker can present an arbitrary certificate, terminate the TLS connection, and intercept ePA traffic. The VAU protocol does not provide an effective fallback because its application-layer certificate validation is also broken in affected versions. The Konnektor session uses self.session.verify set to False while the client authenticates with self.session.cert, so an attacker impersonating the Konnektor can receive the client's mutual TLS certificate exchange and observe smartcard operations. This issue is fixed in version 1.3.0.
References
security-advisories@github.comhttps://github.com/fbeta-GmbH/ePA3-Service-OpenSource/commit/0d94a76aa4d57a849f0c18fb3d6d337ec2505170
security-advisories@github.comhttps://github.com/fbeta-GmbH/ePA3-Service-OpenSource/pull/9
security-advisories@github.comhttps://github.com/fbeta-GmbH/ePA3-Service-OpenSource/releases/tag/1.3.0
security-advisories@github.comhttps://github.com/fbeta-GmbH/ePA3-Service-OpenSource/security/advisories/GHSA-j9m9-pmwv-hwwr
security-advisories@github.comhttps://www.machinespirits.de/advisory/4b68b0
Impacted products
Vendor Product Version
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "product": "ePA3-Service-OpenSource",
          "vendor": "fbeta-GmbH",
          "versions": [
            {
              "status": "affected",
              "version": "\u003c 1.3.0"
            }
          ]
        }
      ],
      "source": "security-advisories@github.com"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "ePA 3.x Integration implements the authorization workflow and writes Medical Information Objects to Germany\u0027s electronic patient record. Prior to 1.3.0, ePA 3.x Integration disables TLS certificate verification for both ePA connections in app/vau/VAUProtokoll.py and Konnektor connections in app/konnektor/Konnektor.py. A network-positioned attacker can present an arbitrary certificate, terminate the TLS connection, and intercept ePA traffic. The VAU protocol does not provide an effective fallback because its application-layer certificate validation is also broken in affected versions. The Konnektor session uses self.session.verify set to False while the client authenticates with self.session.cert, so an attacker impersonating the Konnektor can receive the client\u0027s mutual TLS certificate exchange and observe smartcard operations. This issue is fixed in version 1.3.0."
    }
  ],
  "id": "CVE-2026-50578",
  "lastModified": "2026-08-18T18:18:15.373",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 7.5,
          "baseSeverity": "HIGH",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "NONE",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 3.9,
        "impactScore": 3.6,
        "source": "security-advisories@github.com",
        "type": "Secondary"
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2026-50578",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "yes"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "role": "CISA Coordinator",
          "timestamp": "2026-08-18T17:44:33.357494Z",
          "version": "2.0.3"
        }
      }
    ]
  },
  "published": "2026-08-18T17:16:58.933",
  "references": [
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/fbeta-GmbH/ePA3-Service-OpenSource/commit/0d94a76aa4d57a849f0c18fb3d6d337ec2505170"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/fbeta-GmbH/ePA3-Service-OpenSource/pull/9"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/fbeta-GmbH/ePA3-Service-OpenSource/releases/tag/1.3.0"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/fbeta-GmbH/ePA3-Service-OpenSource/security/advisories/GHSA-j9m9-pmwv-hwwr"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://www.machinespirits.de/advisory/4b68b0"
    }
  ],
  "sourceIdentifier": "security-advisories@github.com",
  "vulnStatus": "Received",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-295"
        }
      ],
      "source": "security-advisories@github.com",
      "type": "Secondary"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.