FKIE_CVE-2026-10303

Vulnerability from fkie_nvd - Published: 2026-06-16 20:16 - Updated: 2026-06-17 17:16
Severity
7.4 (High) - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Summary
In ServerCo getssl version 2.49 and prior, the ACME challenge token returned to the client was not strictly validated against RFC 8555 before being used in challenge-file handling, allowing a maliciously crafted token to influence local path/filename usage during validation. An attacker who can supply ACME challenge responses to getssl (for example, a malicious or compromised CA endpoint, or an on-path adversary able to tamper with that response path) could exploit this to achieve unauthorized file write/path traversal effects, usually with elevated privileges, ultimately allowing for remote command injection. This issue appears related in spirit to CVE-2023-38198, and is an instance of CWE-73, "External control of file name or path." Other ACME shell script handlers may be affected by similar issues.
References
44488dab-36db-4358-99f9-bc116477f914https://github.com/srvrco/getssl/pull/896
44488dab-36db-4358-99f9-bc116477f914https://github.com/srvrco/getssl/releases/tag/v2.50
44488dab-36db-4358-99f9-bc116477f914https://remyhax.xyz/posts/reproducing-lawful-tls-wiretapping/
44488dab-36db-4358-99f9-bc116477f914https://www.cve.org/CVERecord?id=CVE-2023-38198
44488dab-36db-4358-99f9-bc116477f914https://www.runzero.com/advisories/serverco-getssl-acme-cmd-injection-cve-2026-10303/
Impacted products
Vendor Product Version
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "getssl",
          "repo": "https://github.com/srvrco/getssl",
          "vendor": "ServerCo",
          "versions": [
            {
              "lessThanOrEqual": "2.49",
              "status": "affected",
              "version": "0",
              "versionType": "custom"
            }
          ]
        }
      ],
      "source": "44488dab-36db-4358-99f9-bc116477f914"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In ServerCo getssl version 2.49 and prior, the ACME challenge token returned to the client was not strictly validated against RFC 8555 before being used in challenge-file handling, allowing a maliciously crafted token to influence local path/filename usage during validation. An attacker who can supply ACME challenge responses to getssl (for example, a malicious or compromised CA endpoint, or an on-path adversary able to tamper with that response path) could exploit this to achieve unauthorized file write/path traversal effects, usually with elevated privileges, ultimately allowing for remote command injection. This issue appears related in spirit to CVE-2023-38198, and is an instance of CWE-73, \"External control of file name or path.\" Other ACME shell script handlers may be affected by similar issues."
    }
  ],
  "id": "CVE-2026-10303",
  "lastModified": "2026-06-17T17:16:41.383",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "HIGH",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 7.4,
          "baseSeverity": "HIGH",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "HIGH",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 2.2,
        "impactScore": 5.2,
        "source": "44488dab-36db-4358-99f9-bc116477f914",
        "type": "Secondary"
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2026-10303",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "no"
            },
            {
              "technicalImpact": "total"
            }
          ],
          "role": "CISA Coordinator",
          "timestamp": "2026-06-17T15:17:32.277126Z",
          "version": "2.0.3"
        }
      }
    ]
  },
  "published": "2026-06-16T20:16:26.963",
  "references": [
    {
      "source": "44488dab-36db-4358-99f9-bc116477f914",
      "url": "https://github.com/srvrco/getssl/pull/896"
    },
    {
      "source": "44488dab-36db-4358-99f9-bc116477f914",
      "url": "https://github.com/srvrco/getssl/releases/tag/v2.50"
    },
    {
      "source": "44488dab-36db-4358-99f9-bc116477f914",
      "url": "https://remyhax.xyz/posts/reproducing-lawful-tls-wiretapping/"
    },
    {
      "source": "44488dab-36db-4358-99f9-bc116477f914",
      "url": "https://www.cve.org/CVERecord?id=CVE-2023-38198"
    },
    {
      "source": "44488dab-36db-4358-99f9-bc116477f914",
      "url": "https://www.runzero.com/advisories/serverco-getssl-acme-cmd-injection-cve-2026-10303/"
    }
  ],
  "sourceIdentifier": "44488dab-36db-4358-99f9-bc116477f914",
  "vulnStatus": "Awaiting Analysis",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-73"
        }
      ],
      "source": "44488dab-36db-4358-99f9-bc116477f914",
      "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.