How severe is GHSA-6c7m-qwxj-mvhp?

GHSA-6c7m-qwxj-mvhp has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-6c7m-qwxj-mvhp?

GHSA-6c7m-qwxj-mvhp affects the following packages: github.com/edgexfoundry/app-functions-sdk-go/v2 (Go), github.com/edgexfoundry/app-functions-sdk-go (Go), github.com/edgexfoundry/app-service-configurable (Go). Ecosystems affected: Go.

How do I fix GHSA-6c7m-qwxj-mvhp?

Update github.com/edgexfoundry/app-functions-sdk-go/v2 to 2.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6c7m-qwxj-mvhp is resolved across your whole dependency graph.

How do I detect GHSA-6c7m-qwxj-mvhp in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/edgexfoundry/app-functions-sdk-go/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-6c7m-qwxj-mvhp if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-6c7m-qwxj-mvhp actively exploited in the wild?

No public exploit code has been indexed for GHSA-6c7m-qwxj-mvhp yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-6c7m-qwxj-mvhp?

GHSA-6c7m-qwxj-mvhp has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 30th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-6c7m-qwxj-mvhp?

GHSA-6c7m-qwxj-mvhp is classified as Broken Cryptographic Algorithm (CWE-327). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-6c7m-qwxj-mvhp published, and has it been updated?

GHSA-6c7m-qwxj-mvhp was published on November 19, 2021 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

MEDIUM severity

Broken encryption in EdgeX FoundryGHSA-6c7m-qwxj-mvhp

MEDIUMFix: edgexfoundry/app-functions-sdk-go@8fa13c6

GHSA-6c7m-qwxj-mvhp is a medium-severity (CVSS 5.4) Broken Cryptographic Algorithm vulnerability in github.com/edgexfoundry/app-functions-sdk-go/v2. A fix is available for github.com/edgexfoundry/app-functions-sdk-go/v2 — see the affected versions and patch details below.

Also known asCVE-2021-41278

Published

Nov 19, 2021

Updated

Jul 8, 2026

Affected

3 pkgs

Patched

2 / 3

Exploits

None indexed

Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs30th percentile — riskier than 30% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

🐹github.com/edgexfoundry/app-functions-sdk-go/v2🐹github.com/edgexfoundry/app-functions-sdk-go🐹github.com/edgexfoundry/app-service-configurable

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Summary

Broken encryption in app-functions-sdk “AES” transform in EdgeX Foundry releases prior to Jakarta allows attackers to decrypt messages via unspecified vectors.

Detailed Description

The app-functions-sdk exports an “aes” transform that user scripts can optionally call to encrypt data in the processing pipeline. No decrypt function is provided. Encryption is not enabled by default, but if used, the level of protection may be less than the user may expects due to a broken implementation in https://github.com/edgexfoundry/app-functions-sdk-go/blob/v1.0.0/pkg/transforms/encryption.go

Version v2.1.0 (EdgeX Foundry Jakarta release and later) of app-functions-sdk-go/v2 deprecates the “aes” transform and provides an improved “aes256” transform in its place. The broken implementation will remain in a deprecated state until it is removed in the next EdgeX major release to avoid breakage of existing software that depends on the broken implementation.

Impact

As the broken transform is a library function that is not invoked by default, users who do not use the AES transform in their processing pipelines are unaffected. Those that are affected are urged to upgrade to the Jakarta EdgeX release and modify processing pipelines to use the new "aes256" transform.

Vulnerable go modules

github.com/edgexfoundry/app-functions-sdk-go < v2.1.0
github.com/edgexfoundry/app-functions-sdk-go/v2 < v2.1.0
github.com/edgexfoundry/app-service-configurable < v2.1.0

Vulnerable containers

https://hub.docker.com/r/edgexfoundry/app-service-configurable >= 2.0.0 < v2.1.0
https://hub.docker.com/r/edgexfoundry/app-service-configurable-arm64 >= 2.0.0 < 2.1.0
https://hub.docker.com/r/edgexfoundry/docker-app-service-configurable < 2.0.0
https://hub.docker.com/r/edgexfoundry/docker-app-service-configurable-arm64 < 2.0.0

Vulnerable Snaps

https://snapcraft.io/edgex-app-service-configurable >= 2.0.0 < 2.1.0

Patches

Upgrade to 2.1.0 version of app-functions-sdk-go/v2, app-service-configurable, and related docker containers shown below and modify user scripts to use the new "aes256" transform in place of the existing "aes" transform.

Patched go modules

github.com/edgexfoundry/app-functions-sdk-go/v2 v2.1.0
github.com/edgexfoundry/app-service-configurable v2.1.0

Modification of user scripts is necessary for full remediation.

Patched containers

Modification of user scripts is necessary for full remediation.

Patched Snaps

https://snapcraft.io/edgex-app-service-configurable >= 2.1.0

Modification of user scripts is necessary for full remediation.

Workarounds

If unable to upgrade, change the processing pipeline to use an HTTPS (TLS 1.3) endpoint to export and skip encryption.

References

For more information

If you have any questions or comments about this advisory:

Contact us in the Slack #security channel
Open an issue in edgex-go
Email us at [email protected]

Affected Packages

3 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/edgexfoundry/app-functions-sdk-go/v2`	all versions	2.1.0`go get github.com/edgexfoundry/app-functions-sdk-go/v2@v2.1.0`
🐹Go	`github.com/edgexfoundry/app-functions-sdk-go`	all versions	No fix
🐹Go	`github.com/edgexfoundry/app-service-configurable`	all versions	2.1.0`go get github.com/edgexfoundry/app-service-configurable@v2.1.0`

Affected Products

3 products · 3 configurations

Application

app service configurableedgexfoundry

< 2.1.0

range

Application

application functions software development kitedgexfoundry

< 2.1.0

range

Application

edgex foundryedgexfoundry

< 2.1.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/edgexfoundry/app-functions-sdk-go/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/edgexfoundry/app-functions-sdk-go/v2 to 2.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6c7m-qwxj-mvhp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Summary Broken encryption in app-functions-sdk “AES” transform in EdgeX Foundry releases prior to Jakarta allows attackers to decrypt messages via unspecified vectors. ### Detailed Description The app-functions-sdk exports an “aes” transform that user scripts can optionally call to encrypt data in the processing pipeline. No decrypt function is provided. Encryption is not enabled by default, but if used, the level of protection may be less than the user may expects due to a broken implementation in https://github.com/edgexfoundry/app-functions-sdk-go/blob/v1.0.0/pkg/transforms/encryptio